Project Number Date
test_Tails_ISO_21653-test-suite-flatpak-uninstall-race 2 15 Jun 2026, 16:12

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 13:8.392 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.132
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given a computer 0.191
And I create a 7200 MiB disk named "old" 0.019
And I plug USB drive "old" 1.036
And I write an old version of the Tails USB image to disk "old" 14.752
When I start Tails from USB drive "old" with network unplugged 1:2.400
Then the boot device has safe access rights 2.886
And Tails is running from USB drive "old" 0.282
And there is no persistence partition on USB drive "old" 0.070
And process "udev-watchdog" is running 0.050
And udev-watchdog is monitoring the correct device 0.297
And I unplug USB drive "old" 0.145
After features/support/hooks.rb:339 1.549
After features/support/hooks.rb:108 0.019
Tags: @product
1:39.526
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.016
Given a computer 0.147
And I start Tails from USB drive "old" with network unplugged and I login 59.441
Then Tails is running from USB drive "old" 0.275
And I create a persistent partition 26.434
And I take note of which tps features are available 5.453
Then a Tails persistence partition exists on USB drive "old" 0.639
And I shutdown Tails and wait for the computer to power off 7.135
After features/support/hooks.rb:339 0.410
After features/support/hooks.rb:108 0.022
Tags: @product
1:44.787
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.016
Given a computer 0.215
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:11.428
Then Tails is running from USB drive "old" 0.273
And all tps features are active 5.055
When I write some files expected to persist 1.420
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.167
And all persistence configuration files have safe access rights 0.366
And all persistent directories from the old Tails version have safe access rights 2.015
And I take note of which tps features are available 5.774
And I shutdown Tails and wait for the computer to power off 4.613
# 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" 13.455
After features/support/hooks.rb:339 0.590
After features/support/hooks.rb:108 0.028
Tags: @product
2:17.031
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.023
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.648
And I log in to a new session 14.792
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.204
And I plug USB drive "to_upgrade" 2.318
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:33.161
Then the running Tails is installed on USB drive "to_upgrade" 16.397
And I unplug USB drive "to_upgrade" 0.294
And I unplug USB drive "__internal" 0.214
After features/support/hooks.rb:339 2.496
After features/support/hooks.rb:108 0.000
Tags: @product
1:23.424
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.025
Given a computer 0.190
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:15.074
Then all tps features from the old Tails version are active 1.130
And Tails is running from USB drive "to_upgrade" 0.331
And the boot device has safe access rights 2.991
And the expected persistent files created with the old Tails version are present in the filesystem 1.303
And all persistent directories from the old Tails version have safe access rights 2.401
After features/support/hooks.rb:339 0.856
After features/support/hooks.rb:108 0.039
Tags: @product @automatic_upgrade
4:17.806
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.019
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.121
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.289
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.325
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.451
When the network is plugged 0.026
And Tor is ready 13.733
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.958
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.618
Given I shutdown Tails and wait for the computer to power off 10.367
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:16.657
Then Tails is running version 6.2~testoverlayfs 0.012
And all tps features are active 5.555
And the file system changes introduced in version 6.2~testoverlayfs are present 0.229
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# 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.233
When the network is plugged 0.013
And Tor is ready 12.401
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.137
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.160
Given I shutdown Tails and wait for the computer to power off 4.459
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:14.051
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 5.655
And the file system changes introduced in version 6.3~testoverlayfs are present 0.454
And only the 6.3~testoverlayfs SquashFS delta is installed 0.054
# 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.148
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.218
When the network is plugged 0.017
And Tor is ready 10.518
Then the Upgrader considers the system as up-to-date 10.699
# 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.450
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.485
After features/support/hooks.rb:339 0.789
After features/support/hooks.rb:108 0.039
Tags: @product @automatic_upgrade
23.682
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.017
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.335
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.264
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.052
And the signing key used by the Upgrader is outdated 0.048
But a current signing key is available on our website 0.000
When the network is plugged 0.024
And Tor is ready 11.495
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.461
After features/support/hooks.rb:339 1.149
After features/support/hooks.rb:108 0.000