Project Number Date
test_Tails_ISO_21736-reject-unsupported-installs 20 24 Oct 2026, 05:57

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:0.682 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:18.022
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.085
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.475
When I start Tails from USB drive "old" with network unplugged 1:1.006
Then the boot device has safe access rights 1.843
And Tails is running from USB drive "old" 0.211
And there is no persistence partition on USB drive "old" 0.032
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.152
And I unplug USB drive "old" 0.125
After features/support/hooks.rb:339 3.582
After features/support/hooks.rb:108 0.047
Tags: @product
1:20.203
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login 46.341
Then Tails is running from USB drive "old" 0.179
And I create a persistent partition 22.945
And I take note of which tps features are available 6.042
Then a Tails persistence partition exists on USB drive "old" 0.541
And I shutdown Tails and wait for the computer to power off 4.077
After features/support/hooks.rb:339 0.094
After features/support/hooks.rb:108 0.006
Tags: @product
1:30.817
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 "old" with network unplugged and I login with persistence enabled 58.529
Then Tails is running from USB drive "old" 0.194
And all tps features are active 6.592
When I write some files expected to persist 0.994
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.131
And all persistence configuration files have safe access rights 0.235
And all persistent directories from the old Tails version have safe access rights 1.391
And I take note of which tps features are available 6.133
And I shutdown Tails and wait for the computer to power off 5.297
# 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.239
After features/support/hooks.rb:339 0.452
After features/support/hooks.rb:108 0.006
Tags: @product
2:10.219
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.035
And I log in to a new session 10.077
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.695
And I plug USB drive "to_upgrade" 2.172
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.626
Then the running Tails is installed on USB drive "to_upgrade" 18.376
And I unplug USB drive "to_upgrade" 0.123
And I unplug USB drive "__internal" 0.111
After features/support/hooks.rb:339 1.554
After features/support/hooks.rb:108 0.000
Tags: @product
1:3.625
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.076
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.148
Then all tps features from the old Tails version are active 0.939
And Tails is running from USB drive "to_upgrade" 0.201
And the boot device has safe access rights 2.018
And the expected persistent files created with the old Tails version are present in the filesystem 0.820
And all persistent directories from the old Tails version have safe access rights 1.420
After features/support/hooks.rb:339 0.523
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
3:20.321
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.190
And no SquashFS delta is installed 0.049
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.206
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.188
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.262
When the network is plugged 0.033
And Tor is ready 12.928
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.323
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.195
Given I shutdown Tails and wait for the computer to power off 5.171
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.920
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 7.313
And the file system changes introduced in version 6.2~testoverlayfs are present 0.176
And only the 6.2~testoverlayfs SquashFS delta is installed 0.059
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.090
# 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.191
When the network is plugged 0.026
And Tor is ready 10.091
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.327
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.444
Given I shutdown Tails and wait for the computer to power off 4.025
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.233
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.571
And the file system changes introduced in version 6.3~testoverlayfs are present 0.352
And only the 6.3~testoverlayfs SquashFS delta is installed 0.044
# 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.149
When the network is plugged 0.032
And Tor is ready 10.069
Then the Upgrader considers the system as up-to-date 0.089
# 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.073
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.302
After features/support/hooks.rb:339 0.978
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
17.472
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.826
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.190
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.042
But a current signing key is available on our website 0.000
When the network is plugged 0.039
And Tor is ready 9.048
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.284
After features/support/hooks.rb:339 0.694
After features/support/hooks.rb:108 0.000