Project Number Date
test_Tails_ISO_21734-bump-snapshot-restore-timeout 4 18 Aug 2026, 20:26

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:56.131 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:21.374
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.115
And I create a 7200 MiB disk named "old" 0.033
And I plug USB drive "old" 1.029
And I write an old version of the Tails USB image to disk "old" 14.705
When I start Tails from USB drive "old" with network unplugged 1:2.460
Then the boot device has safe access rights 2.386
And Tails is running from USB drive "old" 0.218
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.191
And I unplug USB drive "old" 0.133
After features/support/hooks.rb:339 1.661
After features/support/hooks.rb:108 0.005
Tags: @product
1:29.275
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.084
And I start Tails from USB drive "old" with network unplugged and I login 52.421
Then Tails is running from USB drive "old" 0.270
And I create a persistent partition 24.413
And I take note of which tps features are available 7.424
Then a Tails persistence partition exists on USB drive "old" 0.632
And I shutdown Tails and wait for the computer to power off 4.028
After features/support/hooks.rb:339 0.655
After features/support/hooks.rb:108 0.010
Tags: @product
1:40.613
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.647
Then Tails is running from USB drive "old" 0.213
And all tps features are active 8.766
When I write some files expected to persist 1.203
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.175
And all persistence configuration files have safe access rights 0.326
And all persistent directories from the old Tails version have safe access rights 2.043
And I take note of which tps features are available 6.592
And I shutdown Tails and wait for the computer to power off 2.650
# 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.917
After features/support/hooks.rb:339 0.196
After features/support/hooks.rb:108 0.005
Tags: @product
2:14.266
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 5.502
And I log in to a new session 12.733
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.851
And I plug USB drive "to_upgrade" 2.312
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.392
Then the running Tails is installed on USB drive "to_upgrade" 20.193
And I unplug USB drive "to_upgrade" 0.119
And I unplug USB drive "__internal" 0.160
After features/support/hooks.rb:339 4.058
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.936
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.091
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.029
Then all tps features from the old Tails version are active 1.070
And Tails is running from USB drive "to_upgrade" 0.195
And the boot device has safe access rights 2.400
And the expected persistent files created with the old Tails version are present in the filesystem 1.221
And all persistent directories from the old Tails version have safe access rights 1.928
After features/support/hooks.rb:339 0.796
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:43.238
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 6.234
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.192
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
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.287
When the network is plugged 0.036
And Tor is ready 13.495
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.410
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.674
Given I shutdown Tails and wait for the computer to power off 5.415
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.386
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 9.122
And the file system changes introduced in version 6.2~testoverlayfs are present 0.213
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.139
# 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.212
When the network is plugged 0.027
And Tor is ready 10.761
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.966
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.183
Given I shutdown Tails and wait for the computer to power off 3.920
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.659
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.664
And the file system changes introduced in version 6.3~testoverlayfs are present 0.486
And only the 6.3~testoverlayfs SquashFS delta is installed 0.053
# 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.106
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.222
When the network is plugged 0.487
And Tor is ready 10.144
Then the Upgrader considers the system as up-to-date 0.133
# 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.799
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.344
After features/support/hooks.rb:339 0.681
After features/support/hooks.rb:108 0.017
Tags: @product @automatic_upgrade
16.427
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 5.717
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.240
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.039
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 9.440
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.911
After features/support/hooks.rb:339 0.959
After features/support/hooks.rb:108 0.000