Project Number Date
test_Tails_ISO_21720-less-error-prone-emergency-release 1 20 Aug 2026, 10: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:29.414 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:5.984
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.088
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.022
And I write an old version of the Tails USB image to disk "old" 13.974
When I start Tails from USB drive "old" with network unplugged 47.728
Then the boot device has safe access rights 2.516
And Tails is running from USB drive "old" 0.221
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.186
And I unplug USB drive "old" 0.119
After features/support/hooks.rb:339 3.622
After features/support/hooks.rb:108 0.034
Tags: @product
1:25.792
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.128
And I start Tails from USB drive "old" with network unplugged and I login 50.259
Then Tails is running from USB drive "old" 0.238
And I create a persistent partition 25.101
And I take note of which tps features are available 6.922
Then a Tails persistence partition exists on USB drive "old" 0.518
And I shutdown Tails and wait for the computer to power off 2.624
After features/support/hooks.rb:339 0.562
After features/support/hooks.rb:108 0.005
Tags: @product
1:34.763
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.089
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.363
Then Tails is running from USB drive "old" 0.204
And all tps features are active 6.981
When I write some files expected to persist 1.099
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.147
And all persistence configuration files have safe access rights 0.608
And all persistent directories from the old Tails version have safe access rights 1.870
And I take note of which tps features are available 6.677
And I shutdown Tails and wait for the computer to power off 2.585
# 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" 12.135
After features/support/hooks.rb:339 0.573
After features/support/hooks.rb:108 0.006
Tags: @product
2:14.810
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.065
And I log in to a new session 12.828
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.869
And I plug USB drive "to_upgrade" 2.218
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.914
Then the running Tails is installed on USB drive "to_upgrade" 18.667
And I unplug USB drive "to_upgrade" 0.124
And I unplug USB drive "__internal" 0.121
After features/support/hooks.rb:339 3.837
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.276
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.077
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.588
Then all tps features from the old Tails version are active 1.082
And Tails is running from USB drive "to_upgrade" 0.185
And the boot device has safe access rights 2.538
And the expected persistent files created with the old Tails version are present in the filesystem 1.180
And all persistent directories from the old Tails version have safe access rights 1.622
After features/support/hooks.rb:339 0.863
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
3:37.255
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.543
And no SquashFS delta is installed 0.085
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.202
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.230
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.265
When the network is plugged 0.026
And Tor is ready 12.915
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.798
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.455
Given I shutdown Tails and wait for the computer to power off 5.624
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.158
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 8.467
And the file system changes introduced in version 6.2~testoverlayfs are present 0.192
And only the 6.2~testoverlayfs SquashFS delta is installed 0.058
# 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.208
When the network is plugged 0.030
And Tor is ready 10.294
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.854
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.735
Given I shutdown Tails and wait for the computer to power off 3.957
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.386
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 8.257
And the file system changes introduced in version 6.3~testoverlayfs are present 0.388
And only the 6.3~testoverlayfs SquashFS delta is installed 0.038
# 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.100
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.190
When the network is plugged 0.036
And Tor is ready 10.618
Then the Upgrader considers the system as up-to-date 0.129
# 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.498
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.335
After features/support/hooks.rb:339 0.560
After features/support/hooks.rb:108 0.008
Tags: @product @automatic_upgrade
20.532
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 8.202
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.274
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the signing key used by the Upgrader is outdated 0.138
But a current signing key is available on our website 0.000
When the network is plugged 0.063
And Tor is ready 11.467
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.305
After features/support/hooks.rb:339 0.616
After features/support/hooks.rb:108 0.000