Project Number Date
test_Tails_ISO_21736-reject-unsupported-installs 19 23 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 11:6.159 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.668
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.074
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.206
When I start Tails from USB drive "old" with network unplugged 51.957
Then the boot device has safe access rights 1.872
And Tails is running from USB drive "old" 0.189
And there is no persistence partition on USB drive "old" 0.028
And process "udev-watchdog" is running 0.026
And udev-watchdog is monitoring the correct device 0.164
And I unplug USB drive "old" 0.109
After features/support/hooks.rb:339 3.436
After features/support/hooks.rb:108 0.063
Tags: @product
1:16.969
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.081
And I start Tails from USB drive "old" with network unplugged and I login 46.158
Then Tails is running from USB drive "old" 0.185
And I create a persistent partition 21.532
And I take note of which tps features are available 5.913
Then a Tails persistence partition exists on USB drive "old" 0.474
And I shutdown Tails and wait for the computer to power off 2.623
After features/support/hooks.rb:339 0.338
After features/support/hooks.rb:108 0.005
Tags: @product
1:28.434
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.073
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.646
Then Tails is running from USB drive "old" 0.204
And all tps features are active 6.880
When I write some files expected to persist 1.099
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.118
And all persistence configuration files have safe access rights 0.263
And all persistent directories from the old Tails version have safe access rights 1.612
And I take note of which tps features are available 5.716
And I shutdown Tails and wait for the computer to power off 2.504
# 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.315
After features/support/hooks.rb:339 0.369
After features/support/hooks.rb:108 0.005
Tags: @product
2:10.358
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.240
And I log in to a new session 11.142
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.679
And I plug USB drive "to_upgrade" 2.258
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.782
Then the running Tails is installed on USB drive "to_upgrade" 17.034
And I unplug USB drive "to_upgrade" 0.108
And I unplug USB drive "__internal" 0.111
After features/support/hooks.rb:339 1.827
After features/support/hooks.rb:108 0.000
Tags: @product
1:6.091
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 "to_upgrade" with network unplugged and I login with persistence enabled 1:0.472
Then all tps features from the old Tails version are active 1.083
And Tails is running from USB drive "to_upgrade" 0.160
And the boot device has safe access rights 1.956
And the expected persistent files created with the old Tails version are present in the filesystem 0.894
And all persistent directories from the old Tails version have safe access rights 1.447
After features/support/hooks.rb:339 0.560
After features/support/hooks.rb:108 0.005
3:37.879
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.981
And no SquashFS delta is installed 0.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.210
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.208
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.253
When the network is plugged 0.034
And Tor is ready 13.204
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.290
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 3.982
Given I shutdown Tails and wait for the computer to power off 5.254
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.265
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.237
And the file system changes introduced in version 6.2~testoverlayfs are present 0.178
And only the 6.2~testoverlayfs SquashFS delta is installed 0.057
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.101
# 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.150
When the network is plugged 0.026
And Tor is ready 9.958
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.824
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.780
Given I shutdown Tails and wait for the computer to power off 2.524
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.448
Then Tails is running version 6.3~testoverlayfs 0.011
And all tps features are active 7.572
And the file system changes introduced in version 6.3~testoverlayfs are present 0.268
And only the 6.3~testoverlayfs SquashFS delta is installed 0.035
# 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.106
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.160
When the network is plugged 0.051
And Tor is ready 30.058
Then the Upgrader considers the system as up-to-date 0.174
# 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.957
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.362
After features/support/hooks.rb:339 0.982
After features/support/hooks.rb:108 0.018
17.758
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.770
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.194
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.035
And the signing key used by the Upgrader is outdated 0.034
But a current signing key is available on our website 0.000
When the network is plugged 0.037
And Tor is ready 8.090
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.594
After features/support/hooks.rb:339 0.885
After features/support/hooks.rb:108 0.000