Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 14 05 Jun 2026, 19:50

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:6.060 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:14.770
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.059
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.324
When I start Tails from USB drive "old" with network unplugged 57.447
Then the boot device has safe access rights 2.308
And Tails is running from USB drive "old" 0.205
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.039
And udev-watchdog is monitoring the correct device 0.183
And I unplug USB drive "old" 0.134
After features/support/hooks.rb:335 3.847
After features/support/hooks.rb:104 0.006
Tags: @product
1:24.329
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login 51.310
Then Tails is running from USB drive "old" 0.231
And I create a persistent partition 24.005
And I take note of which tps features are available 0.329
Then a Tails persistence partition exists on USB drive "old" 0.514
And I shutdown Tails and wait for the computer to power off 7.887
After features/support/hooks.rb:335 0.571
After features/support/hooks.rb:104 0.007
Tags: @product
1:24.358
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.325
Then Tails is running from USB drive "old" 0.216
And all tps features are active 1.324
When I write some files expected to persist 1.200
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.187
And all persistence configuration files have safe access rights 0.307
And all persistent directories from the old Tails version have safe access rights 1.911
And I take note of which tps features are available 0.196
And I shutdown Tails and wait for the computer to power off 7.968
# 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.667
After features/support/hooks.rb:335 0.470
After features/support/hooks.rb:104 0.007
Tags: @product
2:9.462
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.244
And I log in to a new session 12.023
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.714
And I plug USB drive "to_upgrade" 2.227
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.439
Then the running Tails is installed on USB drive "to_upgrade" 14.540
And I unplug USB drive "to_upgrade" 0.132
And I unplug USB drive "__internal" 0.140
After features/support/hooks.rb:335 2.107
After features/support/hooks.rb:104 0.000
Tags: @product
1:6.440
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.062
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.584
Then all tps features from the old Tails version are active 0.953
And Tails is running from USB drive "to_upgrade" 0.207
And the boot device has safe access rights 2.563
And the expected persistent files created with the old Tails version are present in the filesystem 1.192
And all persistent directories from the old Tails version have safe access rights 1.875
After features/support/hooks.rb:335 0.802
After features/support/hooks.rb:104 0.036
Tags: @product @automatic_upgrade
3:26.931
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.012
And no SquashFS delta is installed 0.054
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.228
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.194
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.371
When the network is plugged 0.013
And Tor is ready 11.952
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.387
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.245
Given I shutdown Tails and wait for the computer to power off 7.023
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.883
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.135
And the file system changes introduced in version 6.2~testoverlayfs are present 0.240
And only the 6.2~testoverlayfs SquashFS delta is installed 0.058
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.167
# 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.192
When the network is plugged 0.017
And Tor is ready 9.507
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.917
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.720
Given I shutdown Tails and wait for the computer to power off 4.033
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.776
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.139
And the file system changes introduced in version 6.3~testoverlayfs are present 0.369
And only the 6.3~testoverlayfs SquashFS delta is installed 0.062
# 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.144
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.205
When the network is plugged 0.020
And Tor is ready 10.783
Then the Upgrader considers the system as up-to-date 10.560
# 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.094
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.352
After features/support/hooks.rb:335 0.934
After features/support/hooks.rb:104 0.010
Tags: @product @automatic_upgrade
19.767
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 7.269
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.191
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
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.018
And Tor is ready 9.828
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.357
After features/support/hooks.rb:335 0.951
After features/support/hooks.rb:104 0.000