Project Number Date
test_Tails_ISO_21734-bump-snapshot-restore-timeout 2 18 Aug 2026, 12:43

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 10:55.367 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
1:6.997
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.087
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 13.444
When I start Tails from USB drive "old" with network unplugged 49.059
Then the boot device has safe access rights 2.675
And Tails is running from USB drive "old" 0.198
And there is no persistence partition on USB drive "old" 0.055
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.249
And I unplug USB drive "old" 0.136
After features/support/hooks.rb:339 3.556
After features/support/hooks.rb:108 0.042
Tags: @product
1:22.558
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login 49.301
Then Tails is running from USB drive "old" 0.267
And I create a persistent partition 22.959
And I take note of which tps features are available 6.816
Then a Tails persistence partition exists on USB drive "old" 0.546
And I shutdown Tails and wait for the computer to power off 2.583
After features/support/hooks.rb:339 0.280
After features/support/hooks.rb:108 0.005
Tags: @product
1:38.005
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.096
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.079
Then Tails is running from USB drive "old" 0.302
And all tps features are active 7.728
When I write some files expected to persist 1.257
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.174
And all persistence configuration files have safe access rights 0.270
And all persistent directories from the old Tails version have safe access rights 1.688
And I take note of which tps features are available 6.263
And I shutdown Tails and wait for the computer to power off 4.121
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 12.022
After features/support/hooks.rb:339 0.340
After features/support/hooks.rb:108 0.005
Tags: @product
2:14.110
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 5.421
And I log in to a new session 13.169
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.006
And I plug USB drive "to_upgrade" 2.252
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.989
Then the running Tails is installed on USB drive "to_upgrade" 19.981
And I unplug USB drive "to_upgrade" 0.140
And I unplug USB drive "__internal" 0.149
After features/support/hooks.rb:339 6.742
After features/support/hooks.rb:108 0.000
Tags: @product
40.286
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Steps
Given a computer 0.090
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 40.195
Known 
Known issue #20282: Error starting GDM with your graphics card (RuntimeError)
./features/step_definitions/common_steps.rb:452:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:240: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:339 5.202 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:16:54)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21734-bump-snapshot-restore-timeout/2/artifact/build-artifacts/01:16:54_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21734-bump-snapshot-restore-timeout/2/artifact/build-artifacts/01:16:54_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21734-bump-snapshot-restore-timeout/2/artifact/build-artifacts/01:16:54_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21734-bump-snapshot-restore-timeout/2/artifact/build-artifacts/01:16:54_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:35.705
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 5.414
And no SquashFS delta is installed 0.189
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.257
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.181
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.314
When the network is plugged 0.025
And Tor is ready 12.220
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.417
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.795
Given I shutdown Tails and wait for the computer to power off 5.519
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.385
Then Tails is running version 6.2~testoverlayfs 0.009
And all tps features are active 10.191
And the file system changes introduced in version 6.2~testoverlayfs are present 0.264
And only the 6.2~testoverlayfs SquashFS delta is installed 0.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.101
# 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.150
When the network is plugged 0.027
And Tor is ready 10.619
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.858
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.367
Given I shutdown Tails and wait for the computer to power off 2.638
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.405
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 8.576
And the file system changes introduced in version 6.3~testoverlayfs are present 0.334
And only the 6.3~testoverlayfs SquashFS delta is installed 0.036
# 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.113
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.193
When the network is plugged 0.040
And Tor is ready 10.363
Then the Upgrader considers the system as up-to-date 0.102
# 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 3.172
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.321
After features/support/hooks.rb:339 0.739
After features/support/hooks.rb:108 0.015
Tags: @product @automatic_upgrade
17.701
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.009
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 5.405
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.248
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the signing key used by the Upgrader is outdated 0.065
But a current signing key is available on our website 0.000
When the network is plugged 0.029
And Tor is ready 10.389
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.528
After features/support/hooks.rb:339 1.021
After features/support/hooks.rb:108 0.000