Project Number Date
test_Tails_ISO_21734-bump-snapshot-restore-timeout 8 22 Aug 2026, 15:56

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:55.874 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:4.589
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.006
Given a computer 0.085
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.831
When I start Tails from USB drive "old" with network unplugged 46.624
Then the boot device has safe access rights 2.460
And Tails is running from USB drive "old" 0.172
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.033
And udev-watchdog is monitoring the correct device 0.158
And I unplug USB drive "old" 0.145
After features/support/hooks.rb:339 1.180
After features/support/hooks.rb:108 0.005
Tags: @product
1:24.914
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.074
And I start Tails from USB drive "old" with network unplugged and I login 49.686
Then Tails is running from USB drive "old" 0.268
And I create a persistent partition 23.799
And I take note of which tps features are available 6.543
Then a Tails persistence partition exists on USB drive "old" 0.500
And I shutdown Tails and wait for the computer to power off 4.040
After features/support/hooks.rb:339 0.393
After features/support/hooks.rb:108 0.005
Tags: @product
1:35.698
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.291
Then Tails is running from USB drive "old" 0.208
And all tps features are active 7.401
When I write some files expected to persist 1.158
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.163
And all persistence configuration files have safe access rights 0.287
And all persistent directories from the old Tails version have safe access rights 1.672
And I take note of which tps features are available 6.522
And I shutdown Tails and wait for the computer to power off 5.216
# 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.699
After features/support/hooks.rb:339 0.188
After features/support/hooks.rb:108 0.005
Tags: @product
2:13.370
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 8.423
And I log in to a new session 12.126
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.579
And I plug USB drive "to_upgrade" 2.202
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.853
Then the running Tails is installed on USB drive "to_upgrade" 18.912
And I unplug USB drive "to_upgrade" 0.143
And I unplug USB drive "__internal" 0.127
After features/support/hooks.rb:339 1.835
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.781
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 "to_upgrade" with network unplugged and I login with persistence enabled 1:1.922
Then all tps features from the old Tails version are active 1.013
And Tails is running from USB drive "to_upgrade" 0.204
And the boot device has safe access rights 2.148
And the expected persistent files created with the old Tails version are present in the filesystem 0.977
And all persistent directories from the old Tails version have safe access rights 1.431
After features/support/hooks.rb:339 0.845
After features/support/hooks.rb:108 0.005
4:10.312
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 with a persistent partition enabled and logged in 41.417
And no SquashFS delta is installed 0.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.207
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.219
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.335
When the network is plugged 0.025
And Tor is ready 13.029
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.131
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.854
Given I shutdown Tails and wait for the computer to power off 5.345
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.354
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.017
And the file system changes introduced in version 6.2~testoverlayfs are present 0.197
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.109
# 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.176
When the network is plugged 0.034
And Tor is ready 10.599
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.325
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.769
Given I shutdown Tails and wait for the computer to power off 4.078
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.828
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.496
And the file system changes introduced in version 6.3~testoverlayfs are present 0.327
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.115
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.179
When the network is plugged 0.029
And Tor is ready 10.383
Then the Upgrader considers the system as up-to-date 10.566
# 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.548
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.370
After features/support/hooks.rb:339 0.665
After features/support/hooks.rb:108 0.008
19.208
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 with a persistent partition enabled and logged in 7.991
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.212
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the signing key used by the Upgrader is outdated 0.057
But a current signing key is available on our website 0.000
When the network is plugged 0.023
And Tor is ready 9.283
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.602
After features/support/hooks.rb:339 0.969
After features/support/hooks.rb:108 0.000