Project Number Date
test_Tails_ISO_21734-bump-snapshot-restore-timeout 7 20 Aug 2026, 16:03

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 12:34.198 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.852
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.120
And I create a 7200 MiB disk named "old" 0.035
And I plug USB drive "old" 1.026
And I write an old version of the Tails USB image to disk "old" 14.733
When I start Tails from USB drive "old" with network unplugged 59.365
Then the boot device has safe access rights 2.963
And Tails is running from USB drive "old" 0.212
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.193
And I unplug USB drive "old" 0.117
After features/support/hooks.rb:339 3.761
After features/support/hooks.rb:108 0.041
Tags: @product
1:29.122
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login 53.553
Then Tails is running from USB drive "old" 0.206
And I create a persistent partition 24.339
And I take note of which tps features are available 6.258
Then a Tails persistence partition exists on USB drive "old" 0.498
And I shutdown Tails and wait for the computer to power off 4.178
After features/support/hooks.rb:339 0.271
After features/support/hooks.rb:108 0.006
Tags: @product
1:40.053
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.089
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.320
Then Tails is running from USB drive "old" 0.351
And all tps features are active 9.766
When I write some files expected to persist 1.128
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.180
And all persistence configuration files have safe access rights 0.278
And all persistent directories from the old Tails version have safe access rights 1.612
And I take note of which tps features are available 6.348
And I shutdown Tails and wait for the computer to power off 4.177
# 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.799
After features/support/hooks.rb:339 0.314
After features/support/hooks.rb:108 0.006
Tags: @product
2:18.906
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 9.577
And I log in to a new session 12.728
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.484
And I plug USB drive "to_upgrade" 2.364
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.553
Then the running Tails is installed on USB drive "to_upgrade" 19.936
And I unplug USB drive "to_upgrade" 0.133
And I unplug USB drive "__internal" 0.127
After features/support/hooks.rb:339 3.928
After features/support/hooks.rb:108 0.000
Tags: @product
1:13.905
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.101
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.499
Then all tps features from the old Tails version are active 1.130
And Tails is running from USB drive "to_upgrade" 0.246
And the boot device has safe access rights 2.389
And the expected persistent files created with the old Tails version are present in the filesystem 0.911
And all persistent directories from the old Tails version have safe access rights 1.627
After features/support/hooks.rb:339 0.742
After features/support/hooks.rb:108 0.032
Tags: @product @automatic_upgrade
4:13.382
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 41.846
And no SquashFS delta is installed 0.105
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.206
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.243
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.337
When the network is plugged 0.026
And Tor is ready 13.163
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.441
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.356
Given I shutdown Tails and wait for the computer to power off 5.490
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.411
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.071
And the file system changes introduced in version 6.2~testoverlayfs are present 0.318
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.107
# 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.159
When the network is plugged 0.022
And Tor is ready 10.496
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.792
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.808
Given I shutdown Tails and wait for the computer to power off 4.118
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.126
Then Tails is running version 6.3~testoverlayfs 0.016
And all tps features are active 8.315
And the file system changes introduced in version 6.3~testoverlayfs are present 0.351
And only the 6.3~testoverlayfs SquashFS delta is installed 0.047
# 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.090
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.169
When the network is plugged 0.030
And Tor is ready 10.487
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.628
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.390
After features/support/hooks.rb:339 1.036
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
19.974
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 8.017
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.247
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
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.023
And Tor is ready 10.518
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.060
After features/support/hooks.rb:339 0.808
After features/support/hooks.rb:108 0.000