Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 53 11 Jul 2026, 20:02

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.929 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:19.388
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.048
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.212
When I start Tails from USB drive "old" with network unplugged 1:1.998
Then the boot device has safe access rights 2.440
And Tails is running from USB drive "old" 0.249
And there is no persistence partition on USB drive "old" 0.044
And process "udev-watchdog" is running 0.046
And udev-watchdog is monitoring the correct device 0.198
And I unplug USB drive "old" 0.127
After features/support/hooks.rb:339 1.365
After features/support/hooks.rb:108 0.005
Tags: @product
1:28.240
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.085
And I start Tails from USB drive "old" with network unplugged and I login 51.384
Then Tails is running from USB drive "old" 0.216
And I create a persistent partition 24.019
And I take note of which tps features are available 3.647
Then a Tails persistence partition exists on USB drive "old" 0.546
And I shutdown Tails and wait for the computer to power off 8.340
After features/support/hooks.rb:339 0.141
After features/support/hooks.rb:108 0.007
Tags: @product
1:34.105
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.058
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.547
Then Tails is running from USB drive "old" 0.200
And all tps features are active 4.586
When I write some files expected to persist 1.223
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.185
And all persistence configuration files have safe access rights 0.301
And all persistent directories from the old Tails version have safe access rights 1.726
And I take note of which tps features are available 3.760
And I shutdown Tails and wait for the computer to power off 7.887
# 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.628
After features/support/hooks.rb:339 0.250
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.012
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.670
And I log in to a new session 11.830
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.898
And I plug USB drive "to_upgrade" 2.218
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.231
Then the running Tails is installed on USB drive "to_upgrade" 14.911
And I unplug USB drive "to_upgrade" 0.125
And I unplug USB drive "__internal" 0.126
After features/support/hooks.rb:339 3.675
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.170
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:2.127
Then all tps features from the old Tails version are active 1.013
And Tails is running from USB drive "to_upgrade" 0.269
And the boot device has safe access rights 2.430
And the expected persistent files created with the old Tails version are present in the filesystem 1.254
And all persistent directories from the old Tails version have safe access rights 2.028
After features/support/hooks.rb:339 0.577
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:41.510
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.991
And no SquashFS delta is installed 0.053
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.236
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.229
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.302
When the network is plugged 0.018
And Tor is ready 12.067
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.762
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.353
Given I shutdown Tails and wait for the computer to power off 6.680
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.317
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 4.547
And the file system changes introduced in version 6.2~testoverlayfs are present 0.232
And only the 6.2~testoverlayfs SquashFS delta is installed 0.042
# 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.193
When the network is plugged 0.013
And Tor is ready 9.460
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.832
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.878
Given I shutdown Tails and wait for the computer to power off 4.223
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.568
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.724
And the file system changes introduced in version 6.3~testoverlayfs are present 0.343
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.138
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.193
When the network is plugged 0.013
And Tor is ready 9.828
Then the Upgrader considers the system as up-to-date 10.528
# 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.125
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.394
After features/support/hooks.rb:339 0.857
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
20.501
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.362
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.225
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 9.701
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.112
After features/support/hooks.rb:339 0.704
After features/support/hooks.rb:108 0.000