Project Number Date
test_Tails_ISO_21720-less-error-prone-emergency-release 2 20 Aug 2026, 13:36

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:49.271 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:7.139
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.128
And I create a 7200 MiB disk named "old" 0.024
And I plug USB drive "old" 1.030
And I write an old version of the Tails USB image to disk "old" 14.174
When I start Tails from USB drive "old" with network unplugged 48.840
Then the boot device has safe access rights 2.324
And Tails is running from USB drive "old" 0.229
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.175
And I unplug USB drive "old" 0.115
After features/support/hooks.rb:339 1.105
After features/support/hooks.rb:108 0.005
Tags: @product
1:24.656
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.098
And I start Tails from USB drive "old" with network unplugged and I login 51.153
Then Tails is running from USB drive "old" 0.237
And I create a persistent partition 22.923
And I take note of which tps features are available 7.024
Then a Tails persistence partition exists on USB drive "old" 0.627
And I shutdown Tails and wait for the computer to power off 2.591
After features/support/hooks.rb:339 0.296
After features/support/hooks.rb:108 0.008
Tags: @product
1:38.992
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.092
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.758
Then Tails is running from USB drive "old" 0.208
And all tps features are active 8.065
When I write some files expected to persist 1.159
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.143
And all persistence configuration files have safe access rights 0.263
And all persistent directories from the old Tails version have safe access rights 1.982
And I take note of which tps features are available 7.325
And I shutdown Tails and wait for the computer to power off 4.000
# 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.991
After features/support/hooks.rb:339 0.405
After features/support/hooks.rb:108 0.011
Tags: @product
2:15.417
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 without a persistent partition and stopped at Tails Greeter's login screen 8.675
And I log in to a new session 11.907
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.771
And I plug USB drive "to_upgrade" 2.290
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.208
Then the running Tails is installed on USB drive "to_upgrade" 19.308
And I unplug USB drive "to_upgrade" 0.124
And I unplug USB drive "__internal" 0.129
After features/support/hooks.rb:339 3.998
After features/support/hooks.rb:108 0.000
Tags: @product
1:14.429
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.098
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:7.783
Then all tps features from the old Tails version are active 1.182
And Tails is running from USB drive "to_upgrade" 0.222
And the boot device has safe access rights 2.328
And the expected persistent files created with the old Tails version are present in the filesystem 1.009
And all persistent directories from the old Tails version have safe access rights 1.804
After features/support/hooks.rb:339 0.793
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:48.984
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.322
And no SquashFS delta is installed 0.088
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.264
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.054
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.246
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.361
When the network is plugged 0.033
And Tor is ready 12.941
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.972
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.627
Given I shutdown Tails and wait for the computer to power off 6.948
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.338
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 8.224
And the file system changes introduced in version 6.2~testoverlayfs are present 0.154
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.105
# 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.229
When the network is plugged 0.026
And Tor is ready 10.593
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.089
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.902
Given I shutdown Tails and wait for the computer to power off 4.333
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.896
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 9.921
And the file system changes introduced in version 6.3~testoverlayfs are present 0.355
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.120
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.220
When the network is plugged 0.037
And Tor is ready 10.817
Then the Upgrader considers the system as up-to-date 10.508
# 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.747
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.404
After features/support/hooks.rb:339 0.903
After features/support/hooks.rb:108 0.045
Tags: @product @automatic_upgrade
19.652
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.469
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.273
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.037
But a current signing key is available on our website 0.000
When the network is plugged 0.034
And Tor is ready 9.797
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.995
After features/support/hooks.rb:339 0.562
After features/support/hooks.rb:108 0.000