Project Number Date
test_Tails_ISO_21736-reject-unsupported-installs 4 08 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:20.182 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:13.110
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.082
And I create a 7200 MiB disk named "old" 0.022
And I plug USB drive "old" 1.025
And I write an old version of the Tails USB image to disk "old" 13.214
When I start Tails from USB drive "old" with network unplugged 55.739
Then the boot device has safe access rights 2.434
And Tails is running from USB drive "old" 0.209
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.182
And I unplug USB drive "old" 0.108
After features/support/hooks.rb:339 1.214
After features/support/hooks.rb:108 0.006
Tags: @product
1:24.428
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.087
And I start Tails from USB drive "old" with network unplugged and I login 49.388
Then Tails is running from USB drive "old" 0.247
And I create a persistent partition 22.701
And I take note of which tps features are available 6.225
Then a Tails persistence partition exists on USB drive "old" 0.559
And I shutdown Tails and wait for the computer to power off 5.218
After features/support/hooks.rb:339 0.465
After features/support/hooks.rb:108 0.005
Tags: @product
1:31.841
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.084
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.580
Then Tails is running from USB drive "old" 0.182
And all tps features are active 7.486
When I write some files expected to persist 1.342
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.151
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.510
And I take note of which tps features are available 6.203
And I shutdown Tails and wait for the computer to power off 2.563
# 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.472
After features/support/hooks.rb:339 0.431
After features/support/hooks.rb:108 0.006
Tags: @product
2:12.730
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.742
And I log in to a new session 11.648
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.615
And I plug USB drive "to_upgrade" 2.251
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.863
Then the running Tails is installed on USB drive "to_upgrade" 18.355
And I unplug USB drive "to_upgrade" 0.121
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:339 1.687
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.400
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 "to_upgrade" with network unplugged and I login with persistence enabled 1:3.837
Then all tps features from the old Tails version are active 1.120
And Tails is running from USB drive "to_upgrade" 0.213
And the boot device has safe access rights 2.365
And the expected persistent files created with the old Tails version are present in the filesystem 1.045
And all persistent directories from the old Tails version have safe access rights 1.733
After features/support/hooks.rb:339 0.881
After features/support/hooks.rb:108 0.007
3:28.312
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 8.475
And no SquashFS delta is installed 0.065
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.200
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.249
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.303
When the network is plugged 0.031
And Tor is ready 12.207
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.923
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.504
Given I shutdown Tails and wait for the computer to power off 5.344
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.651
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 8.031
And the file system changes introduced in version 6.2~testoverlayfs are present 0.215
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.134
# 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.232
When the network is plugged 0.040
And Tor is ready 10.863
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.437
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.966
Given I shutdown Tails and wait for the computer to power off 4.009
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.615
Then Tails is running version 6.3~testoverlayfs 0.004
And all tps features are active 8.015
And the file system changes introduced in version 6.3~testoverlayfs are present 0.366
And only the 6.3~testoverlayfs SquashFS delta is installed 0.054
# 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.111
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.180
When the network is plugged 0.028
And Tor is ready 10.280
Then the Upgrader considers the system as up-to-date 0.131
# 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.181
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.347
After features/support/hooks.rb:339 0.979
After features/support/hooks.rb:108 0.010
19.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 with a persistent partition enabled and logged in 8.094
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.208
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.032
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.034
And Tor is ready 9.484
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.469
After features/support/hooks.rb:339 0.752
After features/support/hooks.rb:108 0.000