Project Number Date
test_Tails_ISO_stable 4825 03 May 2024, 12:31

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 38:8.399 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:1.895
Before features/support/hooks.rb:259 0.005
Given a computer 0.160
And I create a 7200 MiB disk named "old" 0.041
And I plug USB drive "old" 1.044
And I write an old version of the Tails USB image to disk "old" 36.852
When I start Tails from USB drive "old" with network unplugged 1:20.002
Then the boot device has safe access rights 2.844
And Tails is running from USB drive "old" 0.311
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.097
And udev-watchdog is monitoring the correct device 0.301
And I unplug USB drive "old" 0.166
After features/support/hooks.rb:305 3.714
After features/support/hooks.rb:89 0.017
Tags: @product
2:8.130
Before features/support/hooks.rb:259 0.005
Given a computer 0.892
And I start Tails from USB drive "old" with network unplugged and I login 1:21.829
Then Tails is running from USB drive "old" 0.297
And I create a persistent partition 34.513
And I take note of which tps features are available 1.376
Then a Tails persistence partition exists on USB drive "old" 0.785
And I shutdown Tails and wait for the computer to power off 8.436
After features/support/hooks.rb:305 0.129
After features/support/hooks.rb:89 0.008
Tags: @product
2:43.040
Before features/support/hooks.rb:259 0.006
Given a computer 0.153
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:6.096
Then Tails is running from USB drive "old" 0.277
And all tps features are active 2.013
When I write some files expected to persist 1.705
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.195
And all persistence configuration files have safe access rights 0.427
And all persistent directories from the old Tails version have safe access rights 2.549
And I take note of which tps features are available 0.491
And I shutdown Tails and wait for the computer to power off 4.531
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 24.596
After features/support/hooks.rb:305 0.186
After features/support/hooks.rb:89 0.010
Tags: @product
2:33.036
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 12.575
And I log in to a new session 18.527
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.755
And I plug USB drive "to_upgrade" 2.737
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:37.102
Then the running Tails is installed on USB drive "to_upgrade" 18.920
And I unplug USB drive "to_upgrade" 0.248
And I unplug USB drive "__internal" 0.168
After features/support/hooks.rb:305 2.742
After features/support/hooks.rb:89 0.000
Tags: @product
21:51.713
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:259 0.006
Steps
Given a computer 0.160
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 21:51.553
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.845 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:02:05)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4825/artifact/build-artifacts/02:02:05_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4825/artifact/build-artifacts/02:02:05_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
After features/support/hooks.rb:89 0.033
Tags: @product @automatic_upgrade
6:15.580
Before features/support/hooks.rb:259 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.414
And no SquashFS delta is installed 0.075
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.262
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.328
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.415
When the network is plugged 0.035
And Tor is ready 20.752
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.482
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 11.616
Given I shutdown Tails and wait for the computer to power off 8.631
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:57.386
Then Tails is running version 6.2~testoverlayfs 0.011
And all tps features are active 1.984
And the file system changes introduced in version 6.2~testoverlayfs are present 0.306
And only the 6.2~testoverlayfs SquashFS delta is installed 0.069
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.376
# 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.265
When the network is plugged 0.040
And Tor is ready 21.350
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 5.089
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 10.081
Given I shutdown Tails and wait for the computer to power off 4.272
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:49.769
Then Tails is running version 6.3~testoverlayfs 0.022
And all tps features are active 2.010
And the file system changes introduced in version 6.3~testoverlayfs are present 0.459
And only the 6.3~testoverlayfs SquashFS delta is installed 0.073
# 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.416
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.272
When the network is plugged 0.044
And Tor is ready 15.985
Then the Upgrader considers the system as up-to-date 10.756
# 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 14.630
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.839
After features/support/hooks.rb:305 0.846
After features/support/hooks.rb:89 0.015
Tags: @product @automatic_upgrade
35.002
Before features/support/hooks.rb:259 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.229
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.348
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.055
And the signing key used by the Upgrader is outdated 0.805
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 17.953
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.573
After features/support/hooks.rb:305 1.084
After features/support/hooks.rb:89 0.000