Project Number Date
test_Tails_ISO_21736-reject-unsupported-installs 22 26 Oct 2026, 05:59

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:21.549 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:8.320
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.076
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.020
And I write an old version of the Tails USB image to disk "old" 13.374
When I start Tails from USB drive "old" with network unplugged 51.358
Then the boot device has safe access rights 1.974
And Tails is running from USB drive "old" 0.149
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.045
And udev-watchdog is monitoring the correct device 0.144
And I unplug USB drive "old" 0.106
After features/support/hooks.rb:339 3.823
After features/support/hooks.rb:108 0.056
Tags: @product
1:22.471
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.136
And I start Tails from USB drive "old" with network unplugged and I login 48.303
Then Tails is running from USB drive "old" 0.184
And I create a persistent partition 22.785
And I take note of which tps features are available 6.403
Then a Tails persistence partition exists on USB drive "old" 0.581
And I shutdown Tails and wait for the computer to power off 4.074
After features/support/hooks.rb:339 0.375
After features/support/hooks.rb:108 0.005
Tags: @product
1:31.020
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.110
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.256
Then Tails is running from USB drive "old" 0.233
And all tps features are active 7.450
When I write some files expected to persist 1.159
# 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.262
And all persistent directories from the old Tails version have safe access rights 1.398
And I take note of which tps features are available 6.127
And I shutdown Tails and wait for the computer to power off 2.533
# 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.311
After features/support/hooks.rb:339 0.314
After features/support/hooks.rb:108 0.006
Tags: @product
2:13.597
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 8.731
And I log in to a new session 12.352
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.574
And I plug USB drive "to_upgrade" 2.209
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.326
Then the running Tails is installed on USB drive "to_upgrade" 18.178
And I unplug USB drive "to_upgrade" 0.112
And I unplug USB drive "__internal" 0.111
After features/support/hooks.rb:339 1.782
After features/support/hooks.rb:108 0.000
Tags: @product
1:5.939
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.077
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.917
Then all tps features from the old Tails version are active 1.074
And Tails is running from USB drive "to_upgrade" 0.203
And the boot device has safe access rights 2.081
And the expected persistent files created with the old Tails version are present in the filesystem 0.843
And all persistent directories from the old Tails version have safe access rights 1.741
After features/support/hooks.rb:339 0.761
After features/support/hooks.rb:108 0.005
3:40.065
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 8.482
And no SquashFS delta is installed 0.059
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.244
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.241
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.337
When the network is plugged 0.036
And Tor is ready 13.311
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.306
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.583
Given I shutdown Tails and wait for the computer to power off 5.341
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.619
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 9.381
And the file system changes introduced in version 6.2~testoverlayfs are present 0.221
And only the 6.2~testoverlayfs SquashFS delta is installed 0.050
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.136
# 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.174
When the network is plugged 0.035
And Tor is ready 10.626
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.328
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.862
Given I shutdown Tails and wait for the computer to power off 4.244
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.100
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.201
And the file system changes introduced in version 6.3~testoverlayfs are present 0.207
And only the 6.3~testoverlayfs SquashFS delta is installed 0.027
# 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.107
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.221
When the network is plugged 0.025
And Tor is ready 9.860
Then the Upgrader considers the system as up-to-date 10.474
# 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 2.876
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.289
After features/support/hooks.rb:339 0.854
After features/support/hooks.rb:108 0.020
20.134
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.872
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.027
And Tor is ready 9.253
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.677
After features/support/hooks.rb:339 0.655
After features/support/hooks.rb:108 0.000