Project Number Date
test_Tails_ISO_devel 3800 02 May 2025, 13:02

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:6.997 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:2.761
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.189
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.050
And I write an old version of the Tails USB image to disk "old" 30.126
When I start Tails from USB drive "old" with network unplugged 1:27.489
Then the boot device has safe access rights 2.874
And Tails is running from USB drive "old" 0.353
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.102
And udev-watchdog is monitoring the correct device 0.289
And I unplug USB drive "old" 0.175
After features/support/hooks.rb:330 3.733
After features/support/hooks.rb:100 0.009
Tags: @product
2:7.358
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login 1:24.155
Then Tails is running from USB drive "old" 0.335
And I create a persistent partition 31.325
And I take note of which tps features are available 2.183
Then a Tails persistence partition exists on USB drive "old" 0.941
And I shutdown Tails and wait for the computer to power off 8.223
After features/support/hooks.rb:330 0.164
After features/support/hooks.rb:100 0.007
Tags: @product
2:53.311
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.186
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 2:15.415
Then Tails is running from USB drive "old" 0.662
And all tps features are active 1.996
When I write some files expected to persist 1.721
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.251
And all persistence configuration files have safe access rights 0.593
And all persistent directories from the old Tails version have safe access rights 2.651
And I take note of which tps features are available 0.427
And I shutdown Tails and wait for the computer to power off 4.404
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 25.001
After features/support/hooks.rb:330 0.160
After features/support/hooks.rb:100 0.008
Tags: @product
2:36.311
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.887
And I log in to a new session 18.445
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.803
And I plug USB drive "to_upgrade" 2.409
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:34.736
Then the running Tails is installed on USB drive "to_upgrade" 26.619
And I unplug USB drive "to_upgrade" 0.208
And I unplug USB drive "__internal" 0.201
After features/support/hooks.rb:330 2.021
After features/support/hooks.rb:100 0.000
Tags: @product
21:56.606
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given a computer 0.199
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 21:56.407
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:719:in `new'
./features/step_definitions/common_steps.rb:719: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: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:330 10.888 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:59:22)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3800/artifact/build-artifacts/01:59:22_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3800/artifact/build-artifacts/01:59:22_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3800/artifact/build-artifacts/01:59:22_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.011
Tags: @product @automatic_upgrade
6:52.497
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.743
And no SquashFS delta is installed 0.176
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.517
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.091
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.322
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.645
When the network is plugged 0.069
And Tor is ready 21.371
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.868
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 14.089
Given I shutdown Tails and wait for the computer to power off 10.447
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:59.030
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 4.470
And the file system changes introduced in version 6.2~testoverlayfs are present 0.280
And only the 6.2~testoverlayfs SquashFS delta is installed 0.076
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.377
# 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.260
When the network is plugged 0.073
And Tor is ready 48.093
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.576
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 9.805
Given I shutdown Tails and wait for the computer to power off 4.264
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:56.981
Then Tails is running version 6.3~testoverlayfs 0.012
And all tps features are active 2.520
And the file system changes introduced in version 6.3~testoverlayfs are present 0.520
And only the 6.3~testoverlayfs SquashFS delta is installed 0.066
# 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.332
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.291
When the network is plugged 0.067
And Tor is ready 20.271
Then the Upgrader considers the system as up-to-date 0.319
# 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.437
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 2.009
After features/support/hooks.rb:330 0.735
After features/support/hooks.rb:100 0.043
Tags: @product @automatic_upgrade
38.149
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.427
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.849
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.056
And the signing key used by the Upgrader is outdated 0.107
But a current signing key is available on our website 0.000
When the network is plugged 0.073
And Tor is ready 19.889
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6.745
After features/support/hooks.rb:330 1.436
After features/support/hooks.rb:100 0.000