Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 7 02 Jun 2026, 17:21

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:58.524 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:20.508
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.017
Given a computer 0.155
And I create a 7200 MiB disk named "old" 0.036
And I plug USB drive "old" 1.024
And I write an old version of the Tails USB image to disk "old" 14.884
When I start Tails from USB drive "old" with network unplugged 1:0.233
Then the boot device has safe access rights 3.388
And Tails is running from USB drive "old" 0.259
And there is no persistence partition on USB drive "old" 0.055
And process "udev-watchdog" is running 0.067
And udev-watchdog is monitoring the correct device 0.238
And I unplug USB drive "old" 0.164
After features/support/hooks.rb:335 1.761
After features/support/hooks.rb:104 0.012
Tags: @product
1:30.205
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.014
Given a computer 0.118
And I start Tails from USB drive "old" with network unplugged and I login 58.888
Then Tails is running from USB drive "old" 0.298
And I create a persistent partition 25.885
And I take note of which tps features are available 0.378
Then a Tails persistence partition exists on USB drive "old" 0.546
And I shutdown Tails and wait for the computer to power off 4.089
After features/support/hooks.rb:335 0.216
After features/support/hooks.rb:104 0.008
Tags: @product
1:32.948
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.007
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:6.110
Then Tails is running from USB drive "old" 0.231
And all tps features are active 1.552
When I write some files expected to persist 1.463
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.218
And all persistence configuration files have safe access rights 0.340
And all persistent directories from the old Tails version have safe access rights 2.229
And I take note of which tps features are available 0.197
And I shutdown Tails and wait for the computer to power off 7.996
# 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.548
After features/support/hooks.rb:335 0.428
After features/support/hooks.rb:104 0.006
Tags: @product
2:14.677
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 without a persistent partition and stopped at Tails Greeter's login screen 8.227
And I log in to a new session 13.900
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.799
And I plug USB drive "to_upgrade" 2.227
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.951
Then the running Tails is installed on USB drive "to_upgrade" 16.163
And I unplug USB drive "to_upgrade" 0.185
And I unplug USB drive "__internal" 0.223
After features/support/hooks.rb:335 2.806
After features/support/hooks.rb:104 0.000
Tags: @product
1:13.214
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.087
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.521
Then all tps features from the old Tails version are active 1.015
And Tails is running from USB drive "to_upgrade" 0.237
And the boot device has safe access rights 2.753
And the expected persistent files created with the old Tails version are present in the filesystem 1.222
And all persistent directories from the old Tails version have safe access rights 2.376
After features/support/hooks.rb:335 0.649
After features/support/hooks.rb:104 0.018
Tags: @product @automatic_upgrade
3:46.405
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.771
And no SquashFS delta is installed 0.102
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.312
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.233
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.362
When the network is plugged 0.017
And Tor is ready 13.766
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.003
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.808
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:7.973
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.520
And the file system changes introduced in version 6.2~testoverlayfs are present 0.265
And only the 6.2~testoverlayfs SquashFS delta is installed 0.124
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.162
# 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.211
When the network is plugged 0.020
And Tor is ready 10.301
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.902
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.854
Given I shutdown Tails and wait for the computer to power off 4.120
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.743
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.230
And the file system changes introduced in version 6.3~testoverlayfs are present 0.374
And only the 6.3~testoverlayfs SquashFS delta is installed 0.090
# 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.159
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.387
When the network is plugged 0.023
And Tor is ready 11.611
Then the Upgrader considers the system as up-to-date 10.593
# 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.848
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.436
After features/support/hooks.rb:335 1.097
After features/support/hooks.rb:104 0.025
Tags: @product @automatic_upgrade
20.565
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.008
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.734
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.272
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.029
And Tor is ready 10.378
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.040
After features/support/hooks.rb:335 0.684
After features/support/hooks.rb:104 0.000