Project Number Date
test_Tails_ISO_21736-reject-unsupported-installs 3 07 Oct 2026, 06:22

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:54.525 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:22.574
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.124
And I create a 7200 MiB disk named "old" 0.030
And I plug USB drive "old" 1.027
And I write an old version of the Tails USB image to disk "old" 14.024
When I start Tails from USB drive "old" with network unplugged 1:3.843
Then the boot device has safe access rights 2.826
And Tails is running from USB drive "old" 0.269
And there is no persistence partition on USB drive "old" 0.047
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.212
And I unplug USB drive "old" 0.118
After features/support/hooks.rb:339 3.504
After features/support/hooks.rb:108 0.008
Tags: @product
1:27.055
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.103
And I start Tails from USB drive "old" with network unplugged and I login 50.799
Then Tails is running from USB drive "old" 0.271
And I create a persistent partition 23.818
And I take note of which tps features are available 7.446
Then a Tails persistence partition exists on USB drive "old" 0.688
And I shutdown Tails and wait for the computer to power off 3.927
After features/support/hooks.rb:339 0.251
After features/support/hooks.rb:108 0.008
Tags: @product
1:40.717
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.085
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.594
Then Tails is running from USB drive "old" 0.278
And all tps features are active 7.898
When I write some files expected to persist 1.569
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.148
And all persistence configuration files have safe access rights 0.333
And all persistent directories from the old Tails version have safe access rights 2.144
And I take note of which tps features are available 6.603
And I shutdown Tails and wait for the computer to power off 4.195
# 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" 12.865
After features/support/hooks.rb:339 0.107
After features/support/hooks.rb:108 0.005
Tags: @product
2:17.033
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.479
And I log in to a new session 13.855
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.744
And I plug USB drive "to_upgrade" 2.239
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.059
Then the running Tails is installed on USB drive "to_upgrade" 18.686
And I unplug USB drive "to_upgrade" 0.830
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:339 1.769
After features/support/hooks.rb:108 0.000
Tags: @product
1:12.620
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.114
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.538
Then all tps features from the old Tails version are active 1.137
And Tails is running from USB drive "to_upgrade" 0.210
And the boot device has safe access rights 2.378
And the expected persistent files created with the old Tails version are present in the filesystem 1.029
And all persistent directories from the old Tails version have safe access rights 2.211
After features/support/hooks.rb:339 0.582
After features/support/hooks.rb:108 0.006
3:34.587
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.529
And no SquashFS delta is installed 0.053
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.201
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.247
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.353
When the network is plugged 0.033
And Tor is ready 12.183
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.046
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.903
Given I shutdown Tails and wait for the computer to power off 5.253
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.280
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 7.991
And the file system changes introduced in version 6.2~testoverlayfs are present 0.235
And only the 6.2~testoverlayfs SquashFS delta is installed 0.048
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.103
# 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.178
When the network is plugged 0.024
And Tor is ready 10.451
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.340
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.340
Given I shutdown Tails and wait for the computer to power off 2.609
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.112
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 8.964
And the file system changes introduced in version 6.3~testoverlayfs are present 0.372
And only the 6.3~testoverlayfs SquashFS delta is installed 0.048
# 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.108
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.174
When the network is plugged 0.037
And Tor is ready 10.227
Then the Upgrader considers the system as up-to-date 0.084
# 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.627
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.358
After features/support/hooks.rb:339 0.729
After features/support/hooks.rb:108 0.048
19.938
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.367
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.054
And the signing key used by the Upgrader is outdated 0.072
But a current signing key is available on our website 0.000
When the network is plugged 0.031
And Tor is ready 10.851
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.361
After features/support/hooks.rb:339 0.745
After features/support/hooks.rb:108 0.000