Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 8 02 Jun 2026, 20:10

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 12:28.697 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:21.364
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.085
And I create a 7200 MiB disk named "old" 0.009
And I plug USB drive "old" 1.104
And I write an old version of the Tails USB image to disk "old" 14.084
When I start Tails from USB drive "old" with network unplugged 1:1.803
Then the boot device has safe access rights 3.364
And Tails is running from USB drive "old" 0.331
And there is no persistence partition on USB drive "old" 0.077
And process "udev-watchdog" is running 0.063
And udev-watchdog is monitoring the correct device 0.291
And I unplug USB drive "old" 0.146
After features/support/hooks.rb:335 1.620
After features/support/hooks.rb:104 0.012
Tags: @product
1:33.086
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.064
And I start Tails from USB drive "old" with network unplugged and I login 57.181
Then Tails is running from USB drive "old" 0.397
And I create a persistent partition 25.654
And I take note of which tps features are available 0.458
Then a Tails persistence partition exists on USB drive "old" 0.726
And I shutdown Tails and wait for the computer to power off 8.603
After features/support/hooks.rb:335 0.337
After features/support/hooks.rb:104 0.007
Tags: @product
1:33.173
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.068
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.836
Then Tails is running from USB drive "old" 0.341
And all tps features are active 1.213
When I write some files expected to persist 1.469
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.205
And all persistence configuration files have safe access rights 0.313
And all persistent directories from the old Tails version have safe access rights 2.171
And I take note of which tps features are available 0.190
And I shutdown Tails and wait for the computer to power off 8.094
# 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" 13.269
After features/support/hooks.rb:335 0.120
After features/support/hooks.rb:104 0.006
Tags: @product
2:17.600
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 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 8.636
And I log in to a new session 14.863
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.754
And I plug USB drive "to_upgrade" 2.237
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.286
Then the running Tails is installed on USB drive "to_upgrade" 18.417
And I unplug USB drive "to_upgrade" 0.172
And I unplug USB drive "__internal" 0.231
After features/support/hooks.rb:335 2.720
After features/support/hooks.rb:104 0.000
Tags: @product
1:23.459
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.055
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:15.292
Then all tps features from the old Tails version are active 1.304
And Tails is running from USB drive "to_upgrade" 0.399
And the boot device has safe access rights 3.100
And the expected persistent files created with the old Tails version are present in the filesystem 1.221
And all persistent directories from the old Tails version have safe access rights 2.085
After features/support/hooks.rb:335 0.895
After features/support/hooks.rb:104 0.028
Tags: @product @automatic_upgrade
3:58.410
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.305
And no SquashFS delta is installed 0.092
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.326
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.067
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.250
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.446
When the network is plugged 0.039
And Tor is ready 15.133
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.358
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.601
Given I shutdown Tails and wait for the computer to power off 7.010
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.115
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 1.567
And the file system changes introduced in version 6.2~testoverlayfs are present 0.279
And only the 6.2~testoverlayfs SquashFS delta is installed 0.050
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.139
# 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.199
When the network is plugged 0.019
And Tor is ready 11.964
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.939
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.393
Given I shutdown Tails and wait for the computer to power off 4.174
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.590
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.641
And the file system changes introduced in version 6.3~testoverlayfs are present 0.525
And only the 6.3~testoverlayfs SquashFS delta is installed 0.051
# 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.238
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.335
When the network is plugged 0.017
And Tor is ready 12.661
Then the Upgrader considers the system as up-to-date 10.688
# 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.749
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.419
After features/support/hooks.rb:335 0.724
After features/support/hooks.rb:104 0.043
Tags: @product @automatic_upgrade
21.602
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.777
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.322
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.049
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.022
And Tor is ready 10.418
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.966
After features/support/hooks.rb:335 0.719
After features/support/hooks.rb:104 0.000