Project Number Date
test_Tails_ISO_21170-upgrade-trixie-13.5 2 18 May 2026, 16:56

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:38.792 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:9.262
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.058
And I create a 7200 MiB disk named "old" 0.007
And I plug USB drive "old" 1.028
And I write an old version of the Tails USB image to disk "old" 13.176
When I start Tails from USB drive "old" with network unplugged 51.617
Then the boot device has safe access rights 2.715
And Tails is running from USB drive "old" 0.221
And there is no persistence partition on USB drive "old" 0.046
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.199
And I unplug USB drive "old" 0.138
After features/support/hooks.rb:335 1.257
After features/support/hooks.rb:104 0.007
Tags: @product
1:30.012
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.058
And I start Tails from USB drive "old" with network unplugged and I login 56.018
Then Tails is running from USB drive "old" 0.235
And I create a persistent partition 25.529
And I take note of which tps features are available 0.445
Then a Tails persistence partition exists on USB drive "old" 0.555
And I shutdown Tails and wait for the computer to power off 7.170
After features/support/hooks.rb:335 0.375
After features/support/hooks.rb:104 0.006
Tags: @product
1:30.515
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.078
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.673
Then Tails is running from USB drive "old" 0.342
And all tps features are active 1.238
When I write some files expected to persist 1.247
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.188
And all persistence configuration files have safe access rights 0.299
And all persistent directories from the old Tails version have safe access rights 1.759
And I take note of which tps features are available 0.162
And I shutdown Tails and wait for the computer to power off 8.327
# 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.198
After features/support/hooks.rb:335 0.317
After features/support/hooks.rb:104 0.008
Tags: @product
2:11.006
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 7.841
And I log in to a new session 12.028
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.701
And I plug USB drive "to_upgrade" 2.219
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.717
Then the running Tails is installed on USB drive "to_upgrade" 16.153
And I unplug USB drive "to_upgrade" 0.160
And I unplug USB drive "__internal" 0.185
After features/support/hooks.rb:335 2.621
After features/support/hooks.rb:104 0.000
Tags: @product
1:13.661
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.083
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.507
Then all tps features from the old Tails version are active 1.514
And Tails is running from USB drive "to_upgrade" 0.271
And the boot device has safe access rights 2.747
And the expected persistent files created with the old Tails version are present in the filesystem 1.348
And all persistent directories from the old Tails version have safe access rights 2.187
After features/support/hooks.rb:335 0.590
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:42.417
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.546
And no SquashFS delta is installed 0.078
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.239
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.257
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.393
When the network is plugged 0.014
And Tor is ready 13.373
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.987
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.444
Given I shutdown Tails and wait for the computer to power off 9.455
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.805
Then Tails is running version 6.2~testoverlayfs 0.015
And all tps features are active 1.147
And the file system changes introduced in version 6.2~testoverlayfs are present 0.219
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.126
# 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.227
When the network is plugged 0.014
And Tor is ready 10.830
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.188
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.781
Given I shutdown Tails and wait for the computer to power off 8.312
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.835
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.100
And the file system changes introduced in version 6.3~testoverlayfs are present 0.428
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.133
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.172
When the network is plugged 0.015
And Tor is ready 11.562
Then the Upgrader considers the system as up-to-date 10.616
# 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 4.505
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.406
After features/support/hooks.rb:335 1.011
After features/support/hooks.rb:104 0.012
Tags: @product @automatic_upgrade
21.916
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.142
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.255
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.052
But a current signing key is available on our website 0.000
When the network is plugged 0.017
And Tor is ready 10.596
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.804
After features/support/hooks.rb:335 0.952
After features/support/hooks.rb:104 0.000