Project Number Date
test_Tails_ISO_21373-poweroff-inhibit 26 12 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:31.487 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:10.824
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given a computer 0.121
And I create a 7200 MiB disk named "old" 0.018
And I plug USB drive "old" 1.032
And I write an old version of the Tails USB image to disk "old" 12.975
When I start Tails from USB drive "old" with network unplugged 53.421
Then the boot device has safe access rights 2.575
And Tails is running from USB drive "old" 0.224
And there is no persistence partition on USB drive "old" 0.041
And process "udev-watchdog" is running 0.068
And udev-watchdog is monitoring the correct device 0.182
And I unplug USB drive "old" 0.163
After features/support/hooks.rb:339 1.349
After features/support/hooks.rb:108 0.017
Tags: @product
1:24.166
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.012
Given a computer 0.118
And I start Tails from USB drive "old" with network unplugged and I login 51.426
Then Tails is running from USB drive "old" 0.218
And I create a persistent partition 23.500
And I take note of which tps features are available 4.115
Then a Tails persistence partition exists on USB drive "old" 0.492
And I shutdown Tails and wait for the computer to power off 4.294
After features/support/hooks.rb:339 0.159
After features/support/hooks.rb:108 0.023
Tags: @product
1:31.982
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.025
Given a computer 0.128
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.543
Then Tails is running from USB drive "old" 0.201
And all tps features are active 4.575
When I write some files expected to persist 1.226
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.163
And all persistence configuration files have safe access rights 0.265
And all persistent directories from the old Tails version have safe access rights 2.074
And I take note of which tps features are available 3.650
And I shutdown Tails and wait for the computer to power off 4.384
# 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.771
After features/support/hooks.rb:339 0.314
After features/support/hooks.rb:108 0.018
Tags: @product
2:9.142
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.972
And I log in to a new session 11.372
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.757
And I plug USB drive "to_upgrade" 2.195
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.257
Then the running Tails is installed on USB drive "to_upgrade" 15.314
And I unplug USB drive "to_upgrade" 0.138
And I unplug USB drive "__internal" 0.134
After features/support/hooks.rb:339 1.962
After features/support/hooks.rb:108 0.000
Tags: @product
1:9.988
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.014
Given a computer 0.120
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.049
Then all tps features from the old Tails version are active 1.093
And Tails is running from USB drive "to_upgrade" 0.283
And the boot device has safe access rights 2.370
And the expected persistent files created with the old Tails version are present in the filesystem 1.242
And all persistent directories from the old Tails version have safe access rights 1.826
After features/support/hooks.rb:339 0.749
After features/support/hooks.rb:108 0.017
Tags: @product @automatic_upgrade
3:45.186
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.399
And no SquashFS delta is installed 0.060
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.233
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.046
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.244
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.355
When the network is plugged 0.017
And Tor is ready 13.271
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.641
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.661
Given I shutdown Tails and wait for the computer to power off 7.070
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.276
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 4.733
And the file system changes introduced in version 6.2~testoverlayfs are present 0.229
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.128
# 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.204
When the network is plugged 0.012
And Tor is ready 10.797
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.888
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.581
Given I shutdown Tails and wait for the computer to power off 4.273
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.731
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 4.862
And the file system changes introduced in version 6.3~testoverlayfs are present 0.354
And only the 6.3~testoverlayfs SquashFS delta is installed 0.040
# 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.134
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.253
When the network is plugged 0.043
And Tor is ready 10.431
Then the Upgrader considers the system as up-to-date 10.582
# 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.225
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.330
After features/support/hooks.rb:339 0.824
After features/support/hooks.rb:108 0.033
Tags: @product @automatic_upgrade
20.196
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 7.394
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.267
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.013
And Tor is ready 9.722
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.711
After features/support/hooks.rb:339 0.997
After features/support/hooks.rb:108 0.000