Project Number Date
test_Tails_ISO_devel 3395 20 May 2024, 13:25

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 81 1 5 0 0 87 6 1 7 39:16.413 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:3.297
Before features/support/hooks.rb:259 0.009
Given a computer 0.206
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 32.124
When I start Tails from USB drive "old" with network unplugged 1:25.434
Then the boot device has safe access rights 3.316
And Tails is running from USB drive "old" 0.425
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.089
And udev-watchdog is monitoring the correct device 0.308
And I unplug USB drive "old" 0.226
After features/support/hooks.rb:305 6.918
After features/support/hooks.rb:89 0.012
Tags: @product
2:19.031
Before features/support/hooks.rb:259 0.008
Given a computer 0.196
And I start Tails from USB drive "old" with network unplugged and I login 1:27.985
Then Tails is running from USB drive "old" 0.383
And I create a persistent partition 37.133
And I take note of which tps features are available 1.620
Then a Tails persistence partition exists on USB drive "old" 0.869
And I shutdown Tails and wait for the computer to power off 10.842
After features/support/hooks.rb:305 0.166
After features/support/hooks.rb:89 0.009
Tags: @product
2:54.360
Before features/support/hooks.rb:259 0.006
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:16.387
Then Tails is running from USB drive "old" 0.409
And all tps features are active 2.028
When I write some files expected to persist 1.786
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.236
And all persistence configuration files have safe access rights 0.396
And all persistent directories from the old Tails version have safe access rights 2.890
And I take note of which tps features are available 0.502
And I shutdown Tails and wait for the computer to power off 4.185
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.339
After features/support/hooks.rb:305 0.121
After features/support/hooks.rb:89 0.012
Tags: @product
2:51.913
Before features/support/hooks.rb:259 0.006
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 20.221
And I log in to a new session 21.479
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.578
And I plug USB drive "to_upgrade" 2.465
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:45.734
Then the running Tails is installed on USB drive "to_upgrade" 20.034
And I unplug USB drive "to_upgrade" 0.223
And I unplug USB drive "__internal" 0.175
After features/support/hooks.rb:305 2.117
After features/support/hooks.rb:89 0.000
Tags: @product
22:4.086
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:259 0.009
Steps
Given a computer 0.207
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 22:3.878
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:711:in `new'
./features/step_definitions/common_steps.rb:711:in `/^all notifications have disappeared$/'
./features/step_definitions/common_steps.rb:295: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:73:in `And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled'
Then all tps features from the old Tails version are active 0.000
And Tails is running from USB drive "to_upgrade" 0.000
And the boot device has safe access rights 0.000
And the expected persistent files created with the old Tails version are present in the filesystem 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
After features/support/hooks.rb:305 9.789 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:12:29)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3395/artifact/build-artifacts/02:12:29_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3395/artifact/build-artifacts/02:12:29_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
After features/support/hooks.rb:89 0.012
Tags: @product @automatic_upgrade
6:25.457
Before features/support/hooks.rb:259 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.792
And no SquashFS delta is installed 0.173
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.345
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.059
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.285
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.444
When the network is plugged 0.037
And Tor is ready 17.932
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.880
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 13.127
Given I shutdown Tails and wait for the computer to power off 10.210
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:55.657
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 2.367
And the file system changes introduced in version 6.2~testoverlayfs are present 0.298
And only the 6.2~testoverlayfs SquashFS delta is installed 0.073
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.434
# 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.324
When the network is plugged 0.042
And Tor is ready 20.092
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.391
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.382
Given I shutdown Tails and wait for the computer to power off 6.353
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.349
Then Tails is running version 6.3~testoverlayfs 0.013
And all tps features are active 2.040
And the file system changes introduced in version 6.3~testoverlayfs are present 0.555
And only the 6.3~testoverlayfs SquashFS delta is installed 0.077
# 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.404
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.311
When the network is plugged 0.067
And Tor is ready 16.702
Then the Upgrader considers the system as up-to-date 10.838
# 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 15.484
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.892
After features/support/hooks.rb:305 0.675
After features/support/hooks.rb:89 0.024
Tags: @product @automatic_upgrade
38.267
Before features/support/hooks.rb:259 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.033
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.349
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.069
And the signing key used by the Upgrader is outdated 0.532
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 21.964
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 5.283
After features/support/hooks.rb:305 0.907
After features/support/hooks.rb:89 0.000