Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 19 08 Jun 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:21.869 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:8.212
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.006
Given a computer 0.096
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.018
And I write an old version of the Tails USB image to disk "old" 13.413
When I start Tails from USB drive "old" with network unplugged 50.471
Then the boot device has safe access rights 2.567
And Tails is running from USB drive "old" 0.234
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.159
And I unplug USB drive "old" 0.151
After features/support/hooks.rb:335 1.350
After features/support/hooks.rb:104 0.006
Tags: @product
1:28.085
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login 53.700
Then Tails is running from USB drive "old" 0.288
And I create a persistent partition 24.852
And I take note of which tps features are available 0.313
Then a Tails persistence partition exists on USB drive "old" 0.533
And I shutdown Tails and wait for the computer to power off 8.345
After features/support/hooks.rb:335 0.341
After features/support/hooks.rb:104 0.006
Tags: @product
1:24.465
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.055
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.841
Then Tails is running from USB drive "old" 0.262
And all tps features are active 1.253
When I write some files expected to persist 1.333
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.185
And all persistence configuration files have safe access rights 0.320
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.189
And I shutdown Tails and wait for the computer to power off 4.114
# 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.738
After features/support/hooks.rb:335 0.394
After features/support/hooks.rb:104 0.008
Tags: @product
2:12.650
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 without a persistent partition and stopped at Tails Greeter's login screen 8.635
And I log in to a new session 13.555
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.801
And I plug USB drive "to_upgrade" 2.219
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.138
Then the running Tails is installed on USB drive "to_upgrade" 14.919
And I unplug USB drive "to_upgrade" 0.210
And I unplug USB drive "__internal" 0.169
After features/support/hooks.rb:335 0.885
After features/support/hooks.rb:104 0.000
Tags: @product
1:10.813
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.055
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.754
Then all tps features from the old Tails version are active 1.026
And Tails is running from USB drive "to_upgrade" 0.266
And the boot device has safe access rights 2.759
And the expected persistent files created with the old Tails version are present in the filesystem 1.096
And all persistent directories from the old Tails version have safe access rights 1.855
After features/support/hooks.rb:335 0.933
After features/support/hooks.rb:104 0.007
Tags: @product @automatic_upgrade
3:36.970
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.083
And no SquashFS delta is installed 0.092
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.301
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.283
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.417
When the network is plugged 0.016
And Tor is ready 13.668
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.137
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.826
Given I shutdown Tails and wait for the computer to power off 6.902
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.053
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.214
And the file system changes introduced in version 6.2~testoverlayfs are present 0.250
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.132
# 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.238
When the network is plugged 0.018
And Tor is ready 10.335
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.768
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.912
Given I shutdown Tails and wait for the computer to power off 4.048
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.729
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.240
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.047
# 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.150
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.262
When the network is plugged 0.017
And Tor is ready 9.867
Then the Upgrader considers the system as up-to-date 10.669
# 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.378
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.414
After features/support/hooks.rb:335 0.924
After features/support/hooks.rb:104 0.016
Tags: @product @automatic_upgrade
20.672
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.164
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.224
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the signing key used by the Upgrader is outdated 0.047
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 10.629
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.534
After features/support/hooks.rb:335 0.540
After features/support/hooks.rb:104 0.000