Project Number Date
test_Tails_ISO_21734-bump-snapshot-restore-timeout 5 19 Aug 2026, 15:54

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:37.618 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:13.132
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.103
And I create a 7200 MiB disk named "old" 0.026
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.596
When I start Tails from USB drive "old" with network unplugged 55.236
Then the boot device has safe access rights 2.471
And Tails is running from USB drive "old" 0.236
And there is no persistence partition on USB drive "old" 0.064
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.198
And I unplug USB drive "old" 0.129
After features/support/hooks.rb:339 3.468
After features/support/hooks.rb:108 0.013
Tags: @product
1:27.959
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.018
Given a computer 0.114
And I start Tails from USB drive "old" with network unplugged and I login 50.280
Then Tails is running from USB drive "old" 0.299
And I create a persistent partition 24.933
And I take note of which tps features are available 6.634
Then a Tails persistence partition exists on USB drive "old" 0.558
And I shutdown Tails and wait for the computer to power off 5.137
After features/support/hooks.rb:339 0.363
After features/support/hooks.rb:108 0.005
Tags: @product
1:38.618
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.094
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.490
Then Tails is running from USB drive "old" 0.262
And all tps features are active 8.861
When I write some files expected to persist 1.233
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.133
And all persistence configuration files have safe access rights 0.225
And all persistent directories from the old Tails version have safe access rights 1.437
And I take note of which tps features are available 6.363
And I shutdown Tails and wait for the computer to power off 3.958
# 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.556
After features/support/hooks.rb:339 0.206
After features/support/hooks.rb:108 0.006
Tags: @product
2:12.123
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.570
And I log in to a new session 13.391
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.693
And I plug USB drive "to_upgrade" 2.255
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.265
Then the running Tails is installed on USB drive "to_upgrade" 18.641
And I unplug USB drive "to_upgrade" 0.137
And I unplug USB drive "__internal" 0.167
After features/support/hooks.rb:339 1.812
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.328
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.150
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.746
Then all tps features from the old Tails version are active 1.018
And Tails is running from USB drive "to_upgrade" 0.216
And the boot device has safe access rights 2.315
And the expected persistent files created with the old Tails version are present in the filesystem 1.153
And all persistent directories from the old Tails version have safe access rights 1.727
After features/support/hooks.rb:339 0.861
After features/support/hooks.rb:108 0.007
Tags: @product @automatic_upgrade
3:37.759
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 5.889
And no SquashFS delta is installed 0.105
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.298
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.274
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.312
When the network is plugged 0.027
And Tor is ready 13.373
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.061
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.669
Given I shutdown Tails and wait for the computer to power off 5.471
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.058
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.546
And the file system changes introduced in version 6.2~testoverlayfs are present 0.199
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.147
# 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.205
When the network is plugged 0.040
And Tor is ready 10.532
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.902
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.372
Given I shutdown Tails and wait for the computer to power off 3.918
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.367
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.931
And the file system changes introduced in version 6.3~testoverlayfs are present 0.311
And only the 6.3~testoverlayfs SquashFS delta is installed 0.033
# 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.116
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.170
When the network is plugged 0.029
And Tor is ready 10.948
Then the Upgrader considers the system as up-to-date 0.110
# 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.822
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.377
After features/support/hooks.rb:339 0.727
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
17.694
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.866
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.267
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.076
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.060
And Tor is ready 10.295
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.089
After features/support/hooks.rb:339 1.013
After features/support/hooks.rb:108 0.000