Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 48 05 Jul 2026, 20:10

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 12:21.987 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:12.321
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given a computer 0.088
And I create a 7200 MiB disk named "old" 0.014
And I plug USB drive "old" 1.035
And I write an old version of the Tails USB image to disk "old" 13.785
When I start Tails from USB drive "old" with network unplugged 53.706
Then the boot device has safe access rights 2.990
And Tails is running from USB drive "old" 0.255
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.207
And I unplug USB drive "old" 0.143
After features/support/hooks.rb:339 3.797
After features/support/hooks.rb:108 0.058
Tags: @product
1:33.041
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.059
And I start Tails from USB drive "old" with network unplugged and I login 57.804
Then Tails is running from USB drive "old" 0.247
And I create a persistent partition 25.564
And I take note of which tps features are available 4.619
Then a Tails persistence partition exists on USB drive "old" 0.610
And I shutdown Tails and wait for the computer to power off 4.136
After features/support/hooks.rb:339 0.362
After features/support/hooks.rb:108 0.009
Tags: @product
1:44.223
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given a computer 0.077
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:9.771
Then Tails is running from USB drive "old" 0.269
And all tps features are active 5.254
When I write some files expected to persist 1.354
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.166
And all persistence configuration files have safe access rights 0.331
And all persistent directories from the old Tails version have safe access rights 1.896
And I take note of which tps features are available 4.116
And I shutdown Tails and wait for the computer to power off 8.610
# 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.374
After features/support/hooks.rb:339 0.313
After features/support/hooks.rb:108 0.035
Tags: @product
2:15.056
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.053
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.025
And I log in to a new session 14.426
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.956
And I plug USB drive "to_upgrade" 2.274
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.868
Then the running Tails is installed on USB drive "to_upgrade" 16.240
And I unplug USB drive "to_upgrade" 0.129
And I unplug USB drive "__internal" 0.135
After features/support/hooks.rb:339 2.722
After features/support/hooks.rb:108 0.000
Tags: @product
1:16.239
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:9.412
Then all tps features from the old Tails version are active 0.963
And Tails is running from USB drive "to_upgrade" 0.228
And the boot device has safe access rights 2.590
And the expected persistent files created with the old Tails version are present in the filesystem 1.105
And all persistent directories from the old Tails version have safe access rights 1.892
After features/support/hooks.rb:339 1.010
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
4:0.389
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.392
And no SquashFS delta is installed 0.053
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.285
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.266
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.439
When the network is plugged 0.020
And Tor is ready 13.514
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.256
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.513
Given I shutdown Tails and wait for the computer to power off 6.830
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.812
Then Tails is running version 6.2~testoverlayfs 0.020
And all tps features are active 5.689
And the file system changes introduced in version 6.2~testoverlayfs are present 0.237
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.139
# 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.212
When the network is plugged 0.015
And Tor is ready 10.371
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.876
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.643
Given I shutdown Tails and wait for the computer to power off 4.018
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.223
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 5.765
And the file system changes introduced in version 6.3~testoverlayfs are present 0.432
And only the 6.3~testoverlayfs SquashFS delta is installed 0.060
# 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.127
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.204
When the network is plugged 0.019
And Tor is ready 11.582
Then the Upgrader considers the system as up-to-date 10.527
# 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.303
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.420
After features/support/hooks.rb:339 1.075
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
20.715
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.763
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.237
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.086
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 10.673
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.893
After features/support/hooks.rb:339 1.021
After features/support/hooks.rb:108 0.000