Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 24 10 Jun 2026, 20:01

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:38.528 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:13.446
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.072
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.017
And I write an old version of the Tails USB image to disk "old" 13.631
When I start Tails from USB drive "old" with network unplugged 55.124
Then the boot device has safe access rights 2.841
And Tails is running from USB drive "old" 0.237
And there is no persistence partition on USB drive "old" 0.049
And process "udev-watchdog" is running 0.038
And udev-watchdog is monitoring the correct device 0.231
And I unplug USB drive "old" 0.191
After features/support/hooks.rb:335 3.717
After features/support/hooks.rb:104 0.037
Tags: @product
1:30.296
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.070
And I start Tails from USB drive "old" with network unplugged and I login 55.693
Then Tails is running from USB drive "old" 0.270
And I create a persistent partition 25.082
And I take note of which tps features are available 0.343
Then a Tails persistence partition exists on USB drive "old" 0.622
And I shutdown Tails and wait for the computer to power off 8.213
After features/support/hooks.rb:335 0.584
After features/support/hooks.rb:104 0.007
Tags: @product
1:31.288
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.912
Then Tails is running from USB drive "old" 0.301
And all tps features are active 1.316
When I write some files expected to persist 1.394
# 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.363
And all persistent directories from the old Tails version have safe access rights 2.061
And I take note of which tps features are available 0.170
And I shutdown Tails and wait for the computer to power off 8.040
# 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.459
After features/support/hooks.rb:335 0.574
After features/support/hooks.rb:104 0.007
Tags: @product
2:12.709
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.734
And I log in to a new session 13.508
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.859
And I plug USB drive "to_upgrade" 2.223
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.284
Then the running Tails is installed on USB drive "to_upgrade" 14.832
And I unplug USB drive "to_upgrade" 0.131
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:335 2.445
After features/support/hooks.rb:104 0.000
Tags: @product
1:11.349
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.052
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.954
Then all tps features from the old Tails version are active 1.178
And Tails is running from USB drive "to_upgrade" 0.242
And the boot device has safe access rights 2.880
And the expected persistent files created with the old Tails version are present in the filesystem 1.133
And all persistent directories from the old Tails version have safe access rights 1.907
After features/support/hooks.rb:335 0.894
After features/support/hooks.rb:104 0.008
Tags: @product @automatic_upgrade
3:38.206
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 with a persistent partition enabled and logged in 8.259
And no SquashFS delta is installed 0.065
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.336
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.078
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.241
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.392
When the network is plugged 0.039
And Tor is ready 13.503
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.792
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.395
Given I shutdown Tails and wait for the computer to power off 7.189
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.476
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.337
And the file system changes introduced in version 6.2~testoverlayfs are present 0.226
And only the 6.2~testoverlayfs SquashFS delta is installed 0.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.129
# 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.228
When the network is plugged 0.017
And Tor is ready 10.065
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.495
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.963
Given I shutdown Tails and wait for the computer to power off 4.030
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.823
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.390
And the file system changes introduced in version 6.3~testoverlayfs are present 0.415
And only the 6.3~testoverlayfs SquashFS delta is installed 0.041
# 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.156
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.202
When the network is plugged 0.017
And Tor is ready 9.663
Then the Upgrader considers the system as up-to-date 10.598
# 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.187
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.381
After features/support/hooks.rb:335 0.693
After features/support/hooks.rb:104 0.016
Tags: @product @automatic_upgrade
21.232
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.376
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.405
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.087
But a current signing key is available on our website 0.000
When the network is plugged 0.021
And Tor is ready 10.248
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.040
After features/support/hooks.rb:335 1.008
After features/support/hooks.rb:104 0.000