Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 4 31 May 2026, 19:52

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:40.317 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.455
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.053
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.033
And I write an old version of the Tails USB image to disk "old" 13.808
When I start Tails from USB drive "old" with network unplugged 1:1.667
Then the boot device has safe access rights 3.122
And Tails is running from USB drive "old" 0.253
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.234
And I unplug USB drive "old" 0.138
After features/support/hooks.rb:335 1.506
After features/support/hooks.rb:104 0.006
Tags: @product
1:30.414
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.063
And I start Tails from USB drive "old" with network unplugged and I login 55.985
Then Tails is running from USB drive "old" 0.243
And I create a persistent partition 26.071
And I take note of which tps features are available 0.401
Then a Tails persistence partition exists on USB drive "old" 0.760
And I shutdown Tails and wait for the computer to power off 6.886
After features/support/hooks.rb:335 0.523
After features/support/hooks.rb:104 0.008
Tags: @product
1:27.397
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.127
Then Tails is running from USB drive "old" 0.205
And all tps features are active 1.053
When I write some files expected to persist 1.286
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.168
And all persistence configuration files have safe access rights 0.310
And all persistent directories from the old Tails version have safe access rights 1.960
And I take note of which tps features are available 0.189
And I shutdown Tails and wait for the computer to power off 7.070
# 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.952
After features/support/hooks.rb:335 0.496
After features/support/hooks.rb:104 0.006
Tags: @product
2:12.005
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.747
And I log in to a new session 12.773
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.231
And I plug USB drive "to_upgrade" 2.277
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.151
Then the running Tails is installed on USB drive "to_upgrade" 15.564
And I unplug USB drive "to_upgrade" 0.131
And I unplug USB drive "__internal" 0.127
After features/support/hooks.rb:335 2.256
After features/support/hooks.rb:104 0.000
Tags: @product
1:10.988
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.063
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.722
Then all tps features from the old Tails version are active 1.077
And Tails is running from USB drive "to_upgrade" 0.209
And the boot device has safe access rights 2.359
And the expected persistent files created with the old Tails version are present in the filesystem 1.443
And all persistent directories from the old Tails version have safe access rights 2.112
After features/support/hooks.rb:335 0.782
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:38.202
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.209
And no SquashFS delta is installed 0.086
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.206
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.206
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.352
When the network is plugged 0.014
And Tor is ready 13.864
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.898
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.115
Given I shutdown Tails and wait for the computer to power off 7.013
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.757
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 1.325
And the file system changes introduced in version 6.2~testoverlayfs are present 0.271
And only the 6.2~testoverlayfs SquashFS delta is installed 0.055
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.189
# 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.293
When the network is plugged 0.019
And Tor is ready 10.074
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.566
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.535
Given I shutdown Tails and wait for the computer to power off 4.118
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.624
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.118
And the file system changes introduced in version 6.3~testoverlayfs are present 0.344
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.141
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.246
When the network is plugged 0.027
And Tor is ready 11.321
Then the Upgrader considers the system as up-to-date 10.621
# 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 5.051
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.428
After features/support/hooks.rb:335 0.807
After features/support/hooks.rb:104 0.016
Tags: @product @automatic_upgrade
20.853
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.620
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.232
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 10.319
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.574
After features/support/hooks.rb:335 0.993
After features/support/hooks.rb:104 0.000