Project Number Date
test_Tails_ISO_21736-reject-unsupported-installs 21 25 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:8.366 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:2.530
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.086
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 45.255
Then the boot device has safe access rights 2.035
And Tails is running from USB drive "old" 0.247
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.214
And I unplug USB drive "old" 0.174
After features/support/hooks.rb:339 3.592
After features/support/hooks.rb:108 0.028
Tags: @product
1:25.439
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.092
And I start Tails from USB drive "old" with network unplugged and I login 49.291
Then Tails is running from USB drive "old" 0.190
And I create a persistent partition 23.720
And I take note of which tps features are available 6.489
Then a Tails persistence partition exists on USB drive "old" 0.562
And I shutdown Tails and wait for the computer to power off 5.091
After features/support/hooks.rb:339 0.443
After features/support/hooks.rb:108 0.006
Tags: @product
1:31.745
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.083
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.488
Then Tails is running from USB drive "old" 0.198
And all tps features are active 7.019
When I write some files expected to persist 1.032
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.107
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.892
And I take note of which tps features are available 6.401
And I shutdown Tails and wait for the computer to power off 2.638
# 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.622
After features/support/hooks.rb:339 0.601
After features/support/hooks.rb:108 0.016
Tags: @product
2:10.651
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.141
And I log in to a new session 10.364
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.958
And I plug USB drive "to_upgrade" 2.195
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.740
Then the running Tails is installed on USB drive "to_upgrade" 18.029
And I unplug USB drive "to_upgrade" 0.116
And I unplug USB drive "__internal" 0.105
After features/support/hooks.rb:339 0.576
After features/support/hooks.rb:108 0.000
Tags: @product
1:7.676
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.085
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:1.263
Then all tps features from the old Tails version are active 1.048
And Tails is running from USB drive "to_upgrade" 0.209
And the boot device has safe access rights 2.196
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.980
After features/support/hooks.rb:339 0.504
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:31.316
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.364
And no SquashFS delta is installed 0.100
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.196
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.038
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.204
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.337
When the network is plugged 0.039
And Tor is ready 13.078
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.316
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.536
Given I shutdown Tails and wait for the computer to power off 5.198
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.835
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 8.564
And the file system changes introduced in version 6.2~testoverlayfs are present 0.222
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.118
# 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.180
When the network is plugged 0.026
And Tor is ready 10.354
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.870
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.004
Given I shutdown Tails and wait for the computer to power off 4.199
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.889
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.632
And the file system changes introduced in version 6.3~testoverlayfs are present 0.300
And only the 6.3~testoverlayfs SquashFS delta is installed 0.037
# 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.099
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.162
When the network is plugged 0.027
And Tor is ready 10.761
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.129
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.338
After features/support/hooks.rb:339 0.995
After features/support/hooks.rb:108 0.036
Tags: @product @automatic_upgrade
19.006
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.855
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.258
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.041
And the signing key used by the Upgrader is outdated 0.041
But a current signing key is available on our website 0.000
When the network is plugged 0.038
And Tor is ready 9.928
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.843
After features/support/hooks.rb:339 0.678
After features/support/hooks.rb:108 0.000