Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 27 13 Jun 2026, 20:00

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:33.336 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:15.369
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.027
Given a computer 0.133
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.033
And I write an old version of the Tails USB image to disk "old" 12.924
When I start Tails from USB drive "old" with network unplugged 57.777
Then the boot device has safe access rights 2.785
And Tails is running from USB drive "old" 0.233
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.241
And I unplug USB drive "old" 0.132
After features/support/hooks.rb:339 1.574
After features/support/hooks.rb:108 0.019
Tags: @product
1:23.993
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.052
Given a computer 0.115
And I start Tails from USB drive "old" with network unplugged and I login 51.509
Then Tails is running from USB drive "old" 0.245
And I create a persistent partition 24.741
And I take note of which tps features are available 4.091
Then a Tails persistence partition exists on USB drive "old" 0.532
And I shutdown Tails and wait for the computer to power off 2.757
After features/support/hooks.rb:339 0.397
After features/support/hooks.rb:108 0.017
Tags: @product
1:31.333
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.013
Given a computer 0.143
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.479
Then Tails is running from USB drive "old" 0.229
And all tps features are active 4.357
When I write some files expected to persist 1.136
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.177
And all persistence configuration files have safe access rights 0.272
And all persistent directories from the old Tails version have safe access rights 1.946
And I take note of which tps features are available 3.923
And I shutdown Tails and wait for the computer to power off 4.107
# 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.560
After features/support/hooks.rb:339 0.566
After features/support/hooks.rb:108 0.019
Tags: @product
2:9.268
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.868
And I log in to a new session 12.300
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.847
And I plug USB drive "to_upgrade" 2.221
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.875
Then the running Tails is installed on USB drive "to_upgrade" 14.833
And I unplug USB drive "to_upgrade" 0.152
And I unplug USB drive "__internal" 0.168
After features/support/hooks.rb:339 1.824
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.271
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given a computer 0.119
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.552
Then all tps features from the old Tails version are active 0.858
And Tails is running from USB drive "to_upgrade" 0.248
And the boot device has safe access rights 2.395
And the expected persistent files created with the old Tails version are present in the filesystem 1.188
And all persistent directories from the old Tails version have safe access rights 1.909
After features/support/hooks.rb:339 0.974
After features/support/hooks.rb:108 0.017
Tags: @product @automatic_upgrade
3:41.844
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.438
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.220
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
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.298
When the network is plugged 0.014
And Tor is ready 12.117
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.710
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.974
Given I shutdown Tails and wait for the computer to power off 6.901
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.888
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 4.826
And the file system changes introduced in version 6.2~testoverlayfs are present 0.182
And only the 6.2~testoverlayfs SquashFS delta is installed 0.051
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.134
# 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.217
When the network is plugged 0.019
And Tor is ready 10.560
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.941
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.803
Given I shutdown Tails and wait for the computer to power off 4.342
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.584
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 4.787
And the file system changes introduced in version 6.3~testoverlayfs are present 0.327
And only the 6.3~testoverlayfs SquashFS delta is installed 0.042
# 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.160
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.285
When the network is plugged 0.014
And Tor is ready 9.813
Then the Upgrader considers the system as up-to-date 10.553
# 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 3.863
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.411
After features/support/hooks.rb:339 1.067
After features/support/hooks.rb:108 0.035
Tags: @product @automatic_upgrade
21.255
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.041
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.659
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.235
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.053
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 10.435
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.812
After features/support/hooks.rb:339 0.915
After features/support/hooks.rb:108 0.000