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

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:53.507 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.698
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.045
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.013
And I write an old version of the Tails USB image to disk "old" 13.178
When I start Tails from USB drive "old" with network unplugged 57.895
Then the boot device has safe access rights 2.790
And Tails is running from USB drive "old" 0.297
And there is no persistence partition on USB drive "old" 0.050
And process "udev-watchdog" is running 0.093
And udev-watchdog is monitoring the correct device 0.202
And I unplug USB drive "old" 0.123
After features/support/hooks.rb:339 3.625
After features/support/hooks.rb:108 0.005
Tags: @product
1:28.516
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.052
And I start Tails from USB drive "old" with network unplugged and I login 53.161
Then Tails is running from USB drive "old" 0.226
And I create a persistent partition 24.069
And I take note of which tps features are available 3.807
Then a Tails persistence partition exists on USB drive "old" 0.544
And I shutdown Tails and wait for the computer to power off 6.655
After features/support/hooks.rb:339 0.336
After features/support/hooks.rb:108 0.006
Tags: @product
1:32.073
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.045
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.458
Then Tails is running from USB drive "old" 0.208
And all tps features are active 4.905
When I write some files expected to persist 1.266
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.241
And all persistence configuration files have safe access rights 0.296
And all persistent directories from the old Tails version have safe access rights 1.925
And I take note of which tps features are available 3.634
And I shutdown Tails and wait for the computer to power off 4.204
# 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.887
After features/support/hooks.rb:339 0.219
After features/support/hooks.rb:108 0.006
Tags: @product
2:21.439
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 20.811
And I log in to a new session 11.835
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.788
And I plug USB drive "to_upgrade" 2.205
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.041
Then the running Tails is installed on USB drive "to_upgrade" 14.456
And I unplug USB drive "to_upgrade" 0.146
And I unplug USB drive "__internal" 0.154
After features/support/hooks.rb:339 2.651
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.420
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.047
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.785
Then all tps features from the old Tails version are active 0.995
And Tails is running from USB drive "to_upgrade" 0.257
And the boot device has safe access rights 2.349
And the expected persistent files created with the old Tails version are present in the filesystem 1.126
And all persistent directories from the old Tails version have safe access rights 1.857
After features/support/hooks.rb:339 0.784
After features/support/hooks.rb:108 0.019
Tags: @product @automatic_upgrade
3:45.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.984
And no SquashFS delta is installed 0.061
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.228
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.057
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.227
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.326
When the network is plugged 0.016
And Tor is ready 13.159
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.432
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.409
Given I shutdown Tails and wait for the computer to power off 6.749
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.390
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 4.792
And the file system changes introduced in version 6.2~testoverlayfs are present 0.239
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.153
# 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.206
When the network is plugged 0.020
And Tor is ready 10.562
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.390
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.936
Given I shutdown Tails and wait for the computer to power off 4.235
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.287
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 5.024
And the file system changes introduced in version 6.3~testoverlayfs are present 0.397
And only the 6.3~testoverlayfs SquashFS delta is installed 0.048
# 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.126
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.210
When the network is plugged 0.019
And Tor is ready 9.590
Then the Upgrader considers the system as up-to-date 10.548
# 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.390
After features/support/hooks.rb:339 0.802
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
19.847
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.027
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.037
And the signing key used by the Upgrader is outdated 0.037
But a current signing key is available on our website 0.000
When the network is plugged 0.016
And Tor is ready 10.042
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.471
After features/support/hooks.rb:339 0.886
After features/support/hooks.rb:108 0.000