Project Number Date
test_Tails_ISO_21736-reject-unsupported-installs 9 13 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:5.413 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:3.028
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given a computer 0.092
And I create a 7200 MiB disk named "old" 0.020
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.645
When I start Tails from USB drive "old" with network unplugged 45.400
Then the boot device has safe access rights 2.204
And Tails is running from USB drive "old" 0.193
And there is no persistence partition on USB drive "old" 0.045
And process "udev-watchdog" is running 0.041
And udev-watchdog is monitoring the correct device 0.241
And I unplug USB drive "old" 0.120
After features/support/hooks.rb:339 3.658
After features/support/hooks.rb:108 0.009
Tags: @product
1:25.121
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.098
And I start Tails from USB drive "old" with network unplugged and I login 49.454
Then Tails is running from USB drive "old" 0.194
And I create a persistent partition 23.669
And I take note of which tps features are available 7.079
Then a Tails persistence partition exists on USB drive "old" 0.518
And I shutdown Tails and wait for the computer to power off 4.108
After features/support/hooks.rb:339 0.205
After features/support/hooks.rb:108 0.006
Tags: @product
1:32.605
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.089
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:0.521
Then Tails is running from USB drive "old" 0.274
And all tps features are active 7.481
When I write some files expected to persist 1.167
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.142
And all persistence configuration files have safe access rights 0.311
And all persistent directories from the old Tails version have safe access rights 2.240
And I take note of which tps features are available 6.474
And I shutdown Tails and wait for the computer to power off 2.572
# 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.328
After features/support/hooks.rb:339 0.204
After features/support/hooks.rb:108 0.006
Tags: @product
2:11.066
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.542
And I log in to a new session 11.322
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.698
And I plug USB drive "to_upgrade" 2.400
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:30.384
Then the running Tails is installed on USB drive "to_upgrade" 17.469
And I unplug USB drive "to_upgrade" 0.120
And I unplug USB drive "__internal" 0.128
After features/support/hooks.rb:339 1.397
After features/support/hooks.rb:108 0.000
Tags: @product
1:4.503
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.081
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.005
Then all tps features from the old Tails version are active 1.033
And Tails is running from USB drive "to_upgrade" 0.198
And the boot device has safe access rights 1.991
And the expected persistent files created with the old Tails version are present in the filesystem 0.787
And all persistent directories from the old Tails version have safe access rights 1.406
After features/support/hooks.rb:339 0.699
After features/support/hooks.rb:108 0.005
Tags: @product @automatic_upgrade
3:31.895
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.092
And no SquashFS delta is installed 0.053
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.215
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.184
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.337
When the network is plugged 0.029
And Tor is ready 11.119
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.562
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.714
Given I shutdown Tails and wait for the computer to power off 5.162
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.988
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 7.492
And the file system changes introduced in version 6.2~testoverlayfs are present 0.205
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.098
# 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.169
When the network is plugged 0.038
And Tor is ready 10.227
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.291
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 3.432
Given I shutdown Tails and wait for the computer to power off 2.607
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:0.306
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 7.889
And the file system changes introduced in version 6.3~testoverlayfs are present 0.329
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.109
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.167
When the network is plugged 0.027
And Tor is ready 10.142
Then the Upgrader considers the system as up-to-date 10.385
# 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.124
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.261
After features/support/hooks.rb:339 0.891
After features/support/hooks.rb:108 0.025
Tags: @product @automatic_upgrade
17.191
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.606
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.188
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the signing key used by the Upgrader is outdated 0.044
But a current signing key is available on our website 0.000
When the network is plugged 0.040
And Tor is ready 8.987
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.288
After features/support/hooks.rb:339 0.934
After features/support/hooks.rb:108 0.000