Project Number Date
test_Tails_ISO_21909-allow-disabling-busy-persistence-features 1 12 Nov 2026, 19:58

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.480 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:10.496
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.079
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 13.928
When I start Tails from USB drive "old" with network unplugged 52.486
Then the boot device has safe access rights 2.357
And Tails is running from USB drive "old" 0.228
And there is no persistence partition on USB drive "old" 0.037
And process "udev-watchdog" is running 0.036
And udev-watchdog is monitoring the correct device 0.176
And I unplug USB drive "old" 0.128
After features/support/hooks.rb:339 1.189
After features/support/hooks.rb:108 0.012
Tags: @product
1:25.184
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login 50.028
Then Tails is running from USB drive "old" 0.290
And I create a persistent partition 23.538
And I take note of which tps features are available 6.756
Then a Tails persistence partition exists on USB drive "old" 0.498
And I shutdown Tails and wait for the computer to power off 3.995
After features/support/hooks.rb:339 0.109
After features/support/hooks.rb:108 0.006
Tags: @product
1:37.442
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.128
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.872
Then Tails is running from USB drive "old" 0.302
And all tps features are active 8.012
When I write some files expected to persist 1.144
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.191
And all persistence configuration files have safe access rights 0.322
And all persistent directories from the old Tails version have safe access rights 1.478
And I take note of which tps features are available 5.967
And I shutdown Tails and wait for the computer to power off 4.348
# 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.673
After features/support/hooks.rb:339 0.466
After features/support/hooks.rb:108 0.006
Tags: @product
2:15.030
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.399
And I log in to a new session 11.673
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.637
And I plug USB drive "to_upgrade" 2.178
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.561
Then the running Tails is installed on USB drive "to_upgrade" 19.303
And I unplug USB drive "to_upgrade" 0.134
And I unplug USB drive "__internal" 0.141
After features/support/hooks.rb:339 1.780
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.408
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.075
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.749
Then all tps features from the old Tails version are active 1.138
And Tails is running from USB drive "to_upgrade" 0.253
And the boot device has safe access rights 2.083
And the expected persistent files created with the old Tails version are present in the filesystem 1.211
And all persistent directories from the old Tails version have safe access rights 1.894
After features/support/hooks.rb:339 1.001
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:50.107
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.640
And no SquashFS delta is installed 0.057
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.223
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.219
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.395
When the network is plugged 0.030
And Tor is ready 12.701
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.838
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.486
Given I shutdown Tails and wait for the computer to power off 5.512
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.146
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 8.480
And the file system changes introduced in version 6.2~testoverlayfs are present 0.204
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.118
# 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.182
When the network is plugged 0.023
And Tor is ready 10.633
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.331
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.105
Given I shutdown Tails and wait for the computer to power off 3.987
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.192
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 8.860
And the file system changes introduced in version 6.3~testoverlayfs are present 0.368
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.141
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.187
When the network is plugged 0.025
And Tor is ready 10.390
Then the Upgrader considers the system as up-to-date 10.501
# 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.661
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.315
After features/support/hooks.rb:339 0.825
After features/support/hooks.rb:108 0.041
Tags: @product @automatic_upgrade
19.811
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 8.336
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.261
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the signing key used by the Upgrader is outdated 0.041
But a current signing key is available on our website 0.000
When the network is plugged 0.036
And Tor is ready 10.232
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.867
After features/support/hooks.rb:339 0.901
After features/support/hooks.rb:108 0.000