Project Number Date
test_Tails_ISO_devel 3658 22 Jan 2025, 20:37

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 63 1 23 0 0 87 6 1 7 36:17.355 Failed
Tags: @product
Feature Upgrading an old Tails USB installation
As a Tails user If I have an old version of Tails installed on a USB device and the USB device has a Persistent Storage I want to upgrade Tails on it and keep my Persistent Storage in the process
Tags: @product
2:11.118
Before features/support/hooks.rb:269 0.002
Given a computer 0.177
And I create a 7200 MiB disk named "old" 0.061
And I plug USB drive "old" 1.051
And I write an old version of the Tails USB image to disk "old" 35.295
When I start Tails from USB drive "old" with network unplugged 1:29.857
Then the boot device has safe access rights 3.504
And Tails is running from USB drive "old" 0.374
And there is no persistence partition on USB drive "old" 0.079
And process "udev-watchdog" is running 0.101
And udev-watchdog is monitoring the correct device 0.394
And I unplug USB drive "old" 0.219
After features/support/hooks.rb:326 7.324
After features/support/hooks.rb:100 0.006
Tags: @product
2:8.350
Before features/support/hooks.rb:269 0.002
Given a computer 0.185
And I start Tails from USB drive "old" with network unplugged and I login 1:23.528
Then Tails is running from USB drive "old" 0.355
And I create a persistent partition 33.318
And I take note of which tps features are available 1.470
Then a Tails persistence partition exists on USB drive "old" 0.872
And I shutdown Tails and wait for the computer to power off 8.618
After features/support/hooks.rb:326 0.195
After features/support/hooks.rb:100 0.006
Tags: @product
2:56.652
Before features/support/hooks.rb:269 0.002
Given a computer 0.172
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.613
Then Tails is running from USB drive "old" 1.432
And all tps features are active 2.749
When I write some files expected to persist 2.305
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.299
And all persistence configuration files have safe access rights 0.489
And all persistent directories from the old Tails version have safe access rights 3.077
And I take note of which tps features are available 0.560
And I shutdown Tails and wait for the computer to power off 4.095
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.856
After features/support/hooks.rb:326 0.172
After features/support/hooks.rb:100 0.008
Tags: @product
2:44.876
Before features/support/hooks.rb:269 0.003
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.163
And I log in to a new session 22.627
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.180
And I plug USB drive "to_upgrade" 2.456
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:40.462
Then the running Tails is installed on USB drive "to_upgrade" 25.483
And I unplug USB drive "to_upgrade" 0.257
And I unplug USB drive "__internal" 0.245
After features/support/hooks.rb:326 3.307
After features/support/hooks.rb:100 0.000
Tags: @product
2:26.551
Before features/support/hooks.rb:269 0.003
Given a computer 0.231
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 2:16.591
Then all tps features from the old Tails version are active 1.710
And Tails is running from USB drive "to_upgrade" 0.310
And the boot device has safe access rights 3.661
And the expected persistent files created with the old Tails version are present in the filesystem 1.564
And all persistent directories from the old Tails version have safe access rights 2.480
After features/support/hooks.rb:326 0.983
After features/support/hooks.rb:100 0.006
Tags: @product @automatic_upgrade
23:12.157
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:269 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 14.397
And no SquashFS delta is installed 0.204
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.358
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.314
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.454
When the network is plugged 0.089
And Tor is ready 21.243
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.973
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 12.208
Given I shutdown Tails and wait for the computer to power off 8.752
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 22:7.085
execution 
execution expired (RemoteShell::Timeout)
./features/support/helpers/remote_shell.rb:56:in `read'
./features/support/helpers/remote_shell.rb:56:in `block (3 levels) in communicate'
./features/support/helpers/remote_shell.rb:55:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:42:in `loop'
./features/support/helpers/remote_shell.rb:42:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb:174:in `execute'
./features/support/helpers/remote_shell.rb:185:in `initialize'
./features/support/helpers/dogtail.rb:80:in `new'
./features/support/helpers/dogtail.rb:80:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:712:in `new'
./features/step_definitions/common_steps.rb:712:in `/^all notifications have disappeared$/'
./features/step_definitions/common_steps.rb:298:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/usb_upgrade.feature:93:in `When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
Then Tails is running version 6.2~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.2~testoverlayfs are present 0.000
And only the 6.2~testoverlayfs SquashFS delta is installed 0.000
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.000
# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.iuk
# but we need some way to force upgrading a second time in a row
# even if only the initially installed version is considered
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.3~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present 0.000
And only the 6.3~testoverlayfs SquashFS delta is installed 0.000
# Regression test for #17425 (i.e. the Upgrader would propose
# upgrading to the version that's already running)
Given Tails system time is magically synchronized 0.000
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then the Upgrader considers the system as up-to-date 0.000
# Regression test on #8158 (i.e. the IUK's filesystem is not part of the Unsafe Browser's chroot)
And I successfully start the Unsafe Browser 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.000
After features/support/hooks.rb:326 10.847 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 02:43:05)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3658/artifact/build-artifacts/02:43:05_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3658/artifact/build-artifacts/02:43:05_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3658/artifact/build-artifacts/02:43:05_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.008
Tags: @product @automatic_upgrade
37.649
Before features/support/hooks.rb:269 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.752
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.373
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.061
And the signing key used by the Upgrader is outdated 0.069
But a current signing key is available on our website 0.000
When the network is plugged 0.082
And Tor is ready 21.294
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.016
After features/support/hooks.rb:326 0.670
After features/support/hooks.rb:100 0.000