Project Number Date
test_Tails_ISO_21736-reject-unsupported-installs 14 18 Oct 2026, 05:56

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 10:57.630 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:13.801
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.089
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.029
When I start Tails from USB drive "old" with network unplugged 57.075
Then the boot device has safe access rights 2.045
And Tails is running from USB drive "old" 0.197
And there is no persistence partition on USB drive "old" 0.033
And process "udev-watchdog" is running 0.027
And udev-watchdog is monitoring the correct device 0.134
And I unplug USB drive "old" 0.125
After features/support/hooks.rb:339 3.732
After features/support/hooks.rb:108 0.086
Tags: @product
1:20.728
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given a computer 0.088
And I start Tails from USB drive "old" with network unplugged and I login 47.772
Then Tails is running from USB drive "old" 0.196
And I create a persistent partition 22.517
And I take note of which tps features are available 5.899
Then a Tails persistence partition exists on USB drive "old" 0.476
And I shutdown Tails and wait for the computer to power off 3.777
After features/support/hooks.rb:339 0.580
After features/support/hooks.rb:108 0.006
Tags: @product
1:28.248
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.122
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.200
Then Tails is running from USB drive "old" 0.179
And all tps features are active 6.784
When I write some files expected to persist 0.981
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.146
And all persistence configuration files have safe access rights 0.222
And all persistent directories from the old Tails version have safe access rights 1.426
And I take note of which tps features are available 5.516
And I shutdown Tails and wait for the computer to power off 2.581
# 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.086
After features/support/hooks.rb:339 0.548
After features/support/hooks.rb:108 0.005
Tags: @product
2:9.949
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.268
And I log in to a new session 11.827
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.564
And I plug USB drive "to_upgrade" 2.185
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.635
Then the running Tails is installed on USB drive "to_upgrade" 16.186
And I unplug USB drive "to_upgrade" 0.127
And I unplug USB drive "__internal" 0.153
After features/support/hooks.rb:339 1.950
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.854
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.108
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.313
Then all tps features from the old Tails version are active 0.989
And Tails is running from USB drive "to_upgrade" 0.174
And the boot device has safe access rights 1.948
And the expected persistent files created with the old Tails version are present in the filesystem 0.789
And all persistent directories from the old Tails version have safe access rights 1.530
After features/support/hooks.rb:339 0.789
After features/support/hooks.rb:108 0.058
3:20.609
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 with a persistent partition enabled and logged in 7.858
And no SquashFS delta is installed 0.061
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.182
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.189
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.289
When the network is plugged 0.025
And Tor is ready 13.325
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.853
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.703
Given I shutdown Tails and wait for the computer to power off 5.257
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.986
Then Tails is running version 6.2~testoverlayfs 0.013
And all tps features are active 7.498
And the file system changes introduced in version 6.2~testoverlayfs are present 0.180
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.108
# 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.162
When the network is plugged 0.042
And Tor is ready 10.268
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.325
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.556
Given I shutdown Tails and wait for the computer to power off 2.535
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.253
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.119
And the file system changes introduced in version 6.3~testoverlayfs are present 0.310
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.089
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.141
When the network is plugged 0.023
And Tor is ready 10.642
Then the Upgrader considers the system as up-to-date 0.076
# 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.107
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.285
After features/support/hooks.rb:339 0.709
After features/support/hooks.rb:108 0.019
19.438
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.559
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.174
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.032
And the signing key used by the Upgrader is outdated 0.036
But a current signing key is available on our website 0.000
When the network is plugged 0.026
And Tor is ready 10.221
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.387
After features/support/hooks.rb:339 0.670
After features/support/hooks.rb:108 0.000