Project Number Date
test_Tails_ISO_21736-reject-unsupported-installs 12 16 Oct 2026, 05:50

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:3.689 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.324
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.108
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" 12.955
When I start Tails from USB drive "old" with network unplugged 1:1.558
Then the boot device has safe access rights 2.003
And Tails is running from USB drive "old" 0.302
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.040
And udev-watchdog is monitoring the correct device 0.144
And I unplug USB drive "old" 0.116
After features/support/hooks.rb:339 3.764
After features/support/hooks.rb:108 0.015
Tags: @product
1:20.126
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 46.796
Then Tails is running from USB drive "old" 0.204
And I create a persistent partition 22.574
And I take note of which tps features are available 6.068
Then a Tails persistence partition exists on USB drive "old" 0.532
And I shutdown Tails and wait for the computer to power off 3.877
After features/support/hooks.rb:339 0.182
After features/support/hooks.rb:108 0.005
Tags: @product
1:29.996
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.086
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.502
Then Tails is running from USB drive "old" 0.202
And all tps features are active 6.824
When I write some files expected to persist 0.956
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.136
And all persistence configuration files have safe access rights 0.234
And all persistent directories from the old Tails version have safe access rights 1.383
And I take note of which tps features are available 5.608
And I shutdown Tails and wait for the computer to power off 3.979
# 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.081
After features/support/hooks.rb:339 0.292
After features/support/hooks.rb:108 0.005
Tags: @product
2:12.349
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.460
And I log in to a new session 11.708
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.585
And I plug USB drive "to_upgrade" 2.424
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.825
Then the running Tails is installed on USB drive "to_upgrade" 18.087
And I unplug USB drive "to_upgrade" 0.126
And I unplug USB drive "__internal" 0.131
After features/support/hooks.rb:339 1.893
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.484
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.097
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 58.872
Then all tps features from the old Tails version are active 1.014
And Tails is running from USB drive "to_upgrade" 0.208
And the boot device has safe access rights 2.089
And the expected persistent files created with the old Tails version are present in the filesystem 0.825
And all persistent directories from the old Tails version have safe access rights 1.377
After features/support/hooks.rb:339 0.695
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:20.721
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.974
And no SquashFS delta is installed 0.054
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.036
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.300
When the network is plugged 0.026
And Tor is ready 11.275
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.885
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.740
Given I shutdown Tails and wait for the computer to power off 5.395
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.321
Then Tails is running version 6.2~testoverlayfs 0.007
And all tps features are active 7.377
And the file system changes introduced in version 6.2~testoverlayfs are present 0.184
And only the 6.2~testoverlayfs SquashFS delta is installed 0.038
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.119
# 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.184
When the network is plugged 0.038
And Tor is ready 10.651
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.350
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.529
Given I shutdown Tails and wait for the computer to power off 2.565
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.594
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 7.216
And the file system changes introduced in version 6.3~testoverlayfs are present 0.308
And only the 6.3~testoverlayfs SquashFS delta is installed 0.036
# 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.105
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.201
When the network is plugged 0.036
And Tor is ready 11.146
Then the Upgrader considers the system as up-to-date 0.080
# 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.279
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.231
After features/support/hooks.rb:339 0.598
After features/support/hooks.rb:108 0.010
Tags: @product @automatic_upgrade
17.687
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.972
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.048
And the signing key used by the Upgrader is outdated 0.036
But a current signing key is available on our website 0.000
When the network is plugged 0.027
And Tor is ready 9.096
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.296
After features/support/hooks.rb:339 0.966
After features/support/hooks.rb:108 0.000