Project Number Date
test_Tails_ISO_21734-bump-snapshot-restore-timeout 6 20 Aug 2026, 15:10

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 87 0 0 0 0 87 7 0 7 11:57.117 Passed
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:18.934
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.116
And I create a 7200 MiB disk named "old" 0.028
And I plug USB drive "old" 1.025
And I write an old version of the Tails USB image to disk "old" 14.224
When I start Tails from USB drive "old" with network unplugged 1:0.762
Then the boot device has safe access rights 2.140
And Tails is running from USB drive "old" 0.231
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.035
And udev-watchdog is monitoring the correct device 0.194
And I unplug USB drive "old" 0.122
After features/support/hooks.rb:339 1.300
After features/support/hooks.rb:108 0.008
Tags: @product
1:25.030
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login 50.066
Then Tails is running from USB drive "old" 0.249
And I create a persistent partition 23.364
And I take note of which tps features are available 6.555
Then a Tails persistence partition exists on USB drive "old" 0.608
And I shutdown Tails and wait for the computer to power off 4.103
After features/support/hooks.rb:339 0.367
After features/support/hooks.rb:108 0.006
Tags: @product
1:41.249
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.117
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.428
Then Tails is running from USB drive "old" 0.294
And all tps features are active 7.264
When I write some files expected to persist 1.151
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.151
And all persistence configuration files have safe access rights 0.327
And all persistent directories from the old Tails version have safe access rights 1.941
And I take note of which tps features are available 6.896
And I shutdown Tails and wait for the computer to power off 4.085
# 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" 11.590
After features/support/hooks.rb:339 0.558
After features/support/hooks.rb:108 0.013
Tags: @product
2:16.986
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 without a persistent partition and stopped at Tails Greeter's login screen 8.502
And I log in to a new session 14.459
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.704
And I plug USB drive "to_upgrade" 2.208
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.257
Then the running Tails is installed on USB drive "to_upgrade" 18.595
And I unplug USB drive "to_upgrade" 0.118
And I unplug USB drive "__internal" 0.140
After features/support/hooks.rb:339 3.659
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.749
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.086
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.274
Then all tps features from the old Tails version are active 1.066
And Tails is running from USB drive "to_upgrade" 0.222
And the boot device has safe access rights 2.325
And the expected persistent files created with the old Tails version are present in the filesystem 1.069
And all persistent directories from the old Tails version have safe access rights 1.704
After features/support/hooks.rb:339 0.987
After features/support/hooks.rb:108 0.006
3:41.833
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 9.335
And no SquashFS delta is installed 0.090
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.211
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.244
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.326
When the network is plugged 0.036
And Tor is ready 12.687
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.739
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.920
Given I shutdown Tails and wait for the computer to power off 5.304
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.192
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 9.579
And the file system changes introduced in version 6.2~testoverlayfs are present 0.246
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.121
# 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.248
When the network is plugged 0.024
And Tor is ready 10.578
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.275
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.006
Given I shutdown Tails and wait for the computer to power off 2.629
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.226
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 9.555
And the file system changes introduced in version 6.3~testoverlayfs are present 0.376
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.118
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.210
When the network is plugged 0.038
And Tor is ready 10.863
Then the Upgrader considers the system as up-to-date 0.080
# 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 4.043
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.361
After features/support/hooks.rb:339 1.128
After features/support/hooks.rb:108 0.026
21.334
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.458
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.220
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.044
And the signing key used by the Upgrader is outdated 0.055
But a current signing key is available on our website 0.000
When the network is plugged 0.030
And Tor is ready 9.948
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.574
After features/support/hooks.rb:339 0.849
After features/support/hooks.rb:108 0.000