Project Number Date
test_Tails_ISO_21736-reject-unsupported-installs 15 19 Oct 2026, 05:58

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:16.963 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.089
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.136
And I create a 7200 MiB disk named "old" 0.039
And I plug USB drive "old" 1.025
And I write an old version of the Tails USB image to disk "old" 13.089
When I start Tails from USB drive "old" with network unplugged 56.177
Then the boot device has safe access rights 2.057
And Tails is running from USB drive "old" 0.190
And there is no persistence partition on USB drive "old" 0.048
And process "udev-watchdog" is running 0.056
And udev-watchdog is monitoring the correct device 0.154
And I unplug USB drive "old" 0.114
After features/support/hooks.rb:339 3.553
After features/support/hooks.rb:108 0.038
Tags: @product
1:18.150
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login 45.765
Then Tails is running from USB drive "old" 0.200
And I create a persistent partition 21.856
And I take note of which tps features are available 5.714
Then a Tails persistence partition exists on USB drive "old" 0.490
And I shutdown Tails and wait for the computer to power off 4.039
After features/support/hooks.rb:339 0.143
After features/support/hooks.rb:108 0.005
Tags: @product
1:27.420
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.109
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 58.120
Then Tails is running from USB drive "old" 0.187
And all tps features are active 6.459
When I write some files expected to persist 1.096
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.158
And all persistence configuration files have safe access rights 0.258
And all persistent directories from the old Tails version have safe access rights 1.528
And I take note of which tps features are available 5.637
And I shutdown Tails and wait for the computer to power off 2.598
# 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.268
After features/support/hooks.rb:339 0.385
After features/support/hooks.rb:108 0.005
Tags: @product
2:10.910
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 7.943
And I log in to a new session 12.376
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.604
And I plug USB drive "to_upgrade" 2.232
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.421
Then the running Tails is installed on USB drive "to_upgrade" 17.064
And I unplug USB drive "to_upgrade" 0.149
And I unplug USB drive "__internal" 0.119
After features/support/hooks.rb:339 1.659
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.006
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 "to_upgrade" with network unplugged and I login with persistence enabled 58.600
Then all tps features from the old Tails version are active 1.003
And Tails is running from USB drive "to_upgrade" 0.216
And the boot device has safe access rights 1.877
And the expected persistent files created with the old Tails version are present in the filesystem 0.864
And all persistent directories from the old Tails version have safe access rights 1.365
After features/support/hooks.rb:339 0.615
After features/support/hooks.rb:108 0.044
Tags: @product @automatic_upgrade
3:32.244
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 21.065
And no SquashFS delta is installed 0.049
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.198
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.263
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.308
When the network is plugged 0.026
And Tor is ready 10.775
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.448
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.241
Given I shutdown Tails and wait for the computer to power off 5.267
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.270
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.311
And the file system changes introduced in version 6.2~testoverlayfs are present 0.189
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.114
# 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.207
When the network is plugged 0.025
And Tor is ready 10.055
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.838
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.375
Given I shutdown Tails and wait for the computer to power off 2.627
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.720
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.605
And the file system changes introduced in version 6.3~testoverlayfs are present 0.282
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# 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.114
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.213
When the network is plugged 0.025
And Tor is ready 9.858
Then the Upgrader considers the system as up-to-date 0.087
# 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.199
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.328
After features/support/hooks.rb:339 0.606
After features/support/hooks.rb:108 0.011
Tags: @product @automatic_upgrade
31.141
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.010
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 20.788
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.211
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.024
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.035
And Tor is ready 8.178
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.857
After features/support/hooks.rb:339 0.511
After features/support/hooks.rb:108 0.000