Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 46 02 Jul 2026, 23:32

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:42.878 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:18.043
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.049
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.014
And I write an old version of the Tails USB image to disk "old" 13.286
When I start Tails from USB drive "old" with network unplugged 1:0.488
Then the boot device has safe access rights 2.567
And Tails is running from USB drive "old" 0.228
And there is no persistence partition on USB drive "old" 0.039
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.190
And I unplug USB drive "old" 0.126
After features/support/hooks.rb:339 3.540
After features/support/hooks.rb:108 0.030
Tags: @product
1:28.427
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login 52.156
Then Tails is running from USB drive "old" 0.219
And I create a persistent partition 23.633
And I take note of which tps features are available 3.823
Then a Tails persistence partition exists on USB drive "old" 0.522
And I shutdown Tails and wait for the computer to power off 8.022
After features/support/hooks.rb:339 0.434
After features/support/hooks.rb:108 0.006
Tags: @product
1:34.027
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.044
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.436
Then Tails is running from USB drive "old" 0.247
And all tps features are active 4.581
When I write some files expected to persist 1.275
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.188
And all persistence configuration files have safe access rights 0.261
And all persistent directories from the old Tails version have safe access rights 1.751
And I take note of which tps features are available 3.727
And I shutdown Tails and wait for the computer to power off 7.874
# 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.638
After features/support/hooks.rb:339 0.331
After features/support/hooks.rb:108 0.006
Tags: @product
2:9.673
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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.386
And I log in to a new session 11.948
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.678
And I plug USB drive "to_upgrade" 2.216
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.155
Then the running Tails is installed on USB drive "to_upgrade" 15.008
And I unplug USB drive "to_upgrade" 0.146
And I unplug USB drive "__internal" 0.132
After features/support/hooks.rb:339 6.913
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.983
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.045
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.329
Then all tps features from the old Tails version are active 0.977
And Tails is running from USB drive "to_upgrade" 0.217
And the boot device has safe access rights 2.403
And the expected persistent files created with the old Tails version are present in the filesystem 1.160
And all persistent directories from the old Tails version have safe access rights 1.849
After features/support/hooks.rb:339 0.723
After features/support/hooks.rb:108 0.052
Tags: @product @automatic_upgrade
3:43.392
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.059
And no SquashFS delta is installed 0.102
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.200
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.212
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.313
When the network is plugged 0.018
And Tor is ready 13.382
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.330
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.118
Given I shutdown Tails and wait for the computer to power off 6.917
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.294
Then Tails is running version 6.2~testoverlayfs 0.019
And all tps features are active 4.722
And the file system changes introduced in version 6.2~testoverlayfs are present 0.208
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.121
# 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.186
When the network is plugged 0.014
And Tor is ready 10.938
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.397
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.937
Given I shutdown Tails and wait for the computer to power off 2.665
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.814
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.951
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.070
# 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.130
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.186
When the network is plugged 0.021
And Tor is ready 10.550
Then the Upgrader considers the system as up-to-date 10.565
# 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.140
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.349
After features/support/hooks.rb:339 0.987
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
19.329
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.160
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.215
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the signing key used by the Upgrader is outdated 0.054
But a current signing key is available on our website 0.000
When the network is plugged 0.025
And Tor is ready 9.398
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.433
After features/support/hooks.rb:339 0.913
After features/support/hooks.rb:108 0.000