Project Number Date
test_Tails_ISO_21736-reject-unsupported-installs 11 15 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:24.870 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.242
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.019
And I plug USB drive "old" 1.023
And I write an old version of the Tails USB image to disk "old" 12.973
When I start Tails from USB drive "old" with network unplugged 1:1.435
Then the boot device has safe access rights 2.153
And Tails is running from USB drive "old" 0.169
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.181
And I unplug USB drive "old" 0.108
After features/support/hooks.rb:339 1.460
After features/support/hooks.rb:108 0.043
Tags: @product
1:20.749
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.072
And I start Tails from USB drive "old" with network unplugged and I login 47.463
Then Tails is running from USB drive "old" 0.195
And I create a persistent partition 22.078
And I take note of which tps features are available 6.353
Then a Tails persistence partition exists on USB drive "old" 0.477
And I shutdown Tails and wait for the computer to power off 4.108
After features/support/hooks.rb:339 0.558
After features/support/hooks.rb:108 0.005
Tags: @product
1:28.104
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.883
Then Tails is running from USB drive "old" 0.189
And all tps features are active 6.603
When I write some files expected to persist 1.011
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.160
And all persistence configuration files have safe access rights 0.254
And all persistent directories from the old Tails version have safe access rights 1.300
And I take note of which tps features are available 6.018
And I shutdown Tails and wait for the computer to power off 2.535
# 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.064
After features/support/hooks.rb:339 0.166
After features/support/hooks.rb:108 0.005
Tags: @product
2:12.276
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.470
And I log in to a new session 12.473
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.865
And I plug USB drive "to_upgrade" 2.385
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.327
Then the running Tails is installed on USB drive "to_upgrade" 17.510
And I unplug USB drive "to_upgrade" 0.118
And I unplug USB drive "__internal" 0.123
After features/support/hooks.rb:339 1.736
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.362
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.086
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.302
Then all tps features from the old Tails version are active 0.909
And Tails is running from USB drive "to_upgrade" 0.148
And the boot device has safe access rights 1.769
And the expected persistent files created with the old Tails version are present in the filesystem 0.769
And all persistent directories from the old Tails version have safe access rights 1.375
After features/support/hooks.rb:339 0.868
After features/support/hooks.rb:108 0.005
3:43.629
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 20.828
And no SquashFS delta is installed 0.052
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.169
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.223
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.290
When the network is plugged 0.034
And Tor is ready 11.829
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.386
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.042
Given I shutdown Tails and wait for the computer to power off 5.240
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.580
Then Tails is running version 6.2~testoverlayfs 0.021
And all tps features are active 7.295
And the file system changes introduced in version 6.2~testoverlayfs are present 0.225
And only the 6.2~testoverlayfs SquashFS delta is installed 0.041
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.102
# 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.034
And Tor is ready 10.112
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.487
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.490
Given I shutdown Tails and wait for the computer to power off 3.929
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.718
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.388
And the file system changes introduced in version 6.3~testoverlayfs are present 0.326
And only the 6.3~testoverlayfs SquashFS delta is installed 0.059
# 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.233
When the network is plugged 0.030
And Tor is ready 9.990
Then the Upgrader considers the system as up-to-date 10.407
# 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.463
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.270
After features/support/hooks.rb:339 0.688
After features/support/hooks.rb:108 0.030
17.504
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.812
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.185
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the signing key used by the Upgrader is outdated 0.046
But a current signing key is available on our website 0.000
When the network is plugged 0.033
And Tor is ready 7.954
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.417
After features/support/hooks.rb:339 0.742
After features/support/hooks.rb:108 0.000