Project Number Date
test_Tails_ISO_21909-allow-disabling-busy-persistence-features 2 12 Nov 2026, 20:24

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:51.277 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:23.171
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.079
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.694
When I start Tails from USB drive "old" with network unplugged 1:5.438
Then the boot device has safe access rights 2.351
And Tails is running from USB drive "old" 0.187
And there is no persistence partition on USB drive "old" 0.033
And process "udev-watchdog" is running 0.047
And udev-watchdog is monitoring the correct device 0.164
And I unplug USB drive "old" 0.133
After features/support/hooks.rb:339 3.421
After features/support/hooks.rb:108 0.056
Tags: @product
1:25.886
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login 50.425
Then Tails is running from USB drive "old" 0.298
And I create a persistent partition 23.903
And I take note of which tps features are available 6.815
Then a Tails persistence partition exists on USB drive "old" 0.511
And I shutdown Tails and wait for the computer to power off 3.851
After features/support/hooks.rb:339 0.565
After features/support/hooks.rb:108 0.008
Tags: @product
1:38.802
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.101
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.845
Then Tails is running from USB drive "old" 0.322
And all tps features are active 8.125
When I write some files expected to persist 1.173
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.202
And all persistence configuration files have safe access rights 0.229
And all persistent directories from the old Tails version have safe access rights 1.764
And I take note of which tps features are available 6.876
And I shutdown Tails and wait for the computer to power off 4.242
# 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.919
After features/support/hooks.rb:339 0.573
After features/support/hooks.rb:108 0.006
Tags: @product
2:14.639
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 without a persistent partition and stopped at Tails Greeter's login screen 8.988
And I log in to a new session 11.297
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.690
And I plug USB drive "to_upgrade" 2.232
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.004
Then the running Tails is installed on USB drive "to_upgrade" 19.168
And I unplug USB drive "to_upgrade" 0.125
And I unplug USB drive "__internal" 0.133
After features/support/hooks.rb:339 1.676
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.963
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.080
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.001
Then all tps features from the old Tails version are active 1.168
And Tails is running from USB drive "to_upgrade" 0.222
And the boot device has safe access rights 2.458
And the expected persistent files created with the old Tails version are present in the filesystem 1.095
And all persistent directories from the old Tails version have safe access rights 1.935
After features/support/hooks.rb:339 0.782
After features/support/hooks.rb:108 0.012
Tags: @product @automatic_upgrade
3:37.376
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.497
And no SquashFS delta is installed 0.080
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.227
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.026
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.187
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.350
When the network is plugged 0.061
And Tor is ready 13.346
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.310
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.604
Given I shutdown Tails and wait for the computer to power off 5.461
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.070
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 8.366
And the file system changes introduced in version 6.2~testoverlayfs are present 0.188
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.140
# 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.194
When the network is plugged 0.021
And Tor is ready 10.973
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.339
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.073
Given I shutdown Tails and wait for the computer to power off 4.275
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.979
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.714
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.069
# 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.121
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.186
When the network is plugged 0.035
And Tor is ready 10.443
Then the Upgrader considers the system as up-to-date 0.087
# 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 4.168
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.385
After features/support/hooks.rb:339 1.075
After features/support/hooks.rb:108 0.050
Tags: @product @automatic_upgrade
20.438
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.409
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.225
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.027
And Tor is ready 10.749
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.937
After features/support/hooks.rb:339 0.848
After features/support/hooks.rb:108 0.000