Project Number Date
test_Tails_ISO_21653-test-suite-flatpak-uninstall-race 1 15 Jun 2026, 14:47

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 12:38.872 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:12.077
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given a computer 0.164
And I create a 7200 MiB disk named "old" 0.024
And I plug USB drive "old" 1.043
And I write an old version of the Tails USB image to disk "old" 13.852
When I start Tails from USB drive "old" with network unplugged 53.344
Then the boot device has safe access rights 2.837
And Tails is running from USB drive "old" 0.268
And there is no persistence partition on USB drive "old" 0.068
And process "udev-watchdog" is running 0.061
And udev-watchdog is monitoring the correct device 0.221
And I unplug USB drive "old" 0.188
After features/support/hooks.rb:339 1.546
After features/support/hooks.rb:108 0.023
Tags: @product
1:36.097
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.023
Given a computer 0.155
And I start Tails from USB drive "old" with network unplugged and I login 57.592
Then Tails is running from USB drive "old" 0.290
And I create a persistent partition 25.775
And I take note of which tps features are available 4.602
Then a Tails persistence partition exists on USB drive "old" 0.626
And I shutdown Tails and wait for the computer to power off 7.055
After features/support/hooks.rb:339 0.336
After features/support/hooks.rb:108 0.019
Tags: @product
1:43.525
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.019
Given a computer 0.167
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:9.292
Then Tails is running from USB drive "old" 0.271
And all tps features are active 5.154
When I write some files expected to persist 1.466
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.284
And all persistence configuration files have safe access rights 0.467
And all persistent directories from the old Tails version have safe access rights 2.018
And I take note of which tps features are available 4.292
And I shutdown Tails and wait for the computer to power off 7.096
# 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.012
After features/support/hooks.rb:339 0.398
After features/support/hooks.rb:108 0.020
Tags: @product
2:13.256
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.159
And I log in to a new session 12.938
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.858
And I plug USB drive "to_upgrade" 2.259
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.384
Then the running Tails is installed on USB drive "to_upgrade" 16.322
And I unplug USB drive "to_upgrade" 0.187
And I unplug USB drive "__internal" 0.144
After features/support/hooks.rb:339 2.443
After features/support/hooks.rb:108 0.000
Tags: @product
1:17.482
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.011
Given a computer 0.080
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:10.190
Then all tps features from the old Tails version are active 0.951
And Tails is running from USB drive "to_upgrade" 0.250
And the boot device has safe access rights 2.716
And the expected persistent files created with the old Tails version are present in the filesystem 1.212
And all persistent directories from the old Tails version have safe access rights 2.081
After features/support/hooks.rb:339 0.783
After features/support/hooks.rb:108 0.015
Tags: @product @automatic_upgrade
4:14.943
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 21.949
And no SquashFS delta is installed 0.072
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.244
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.050
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.251
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.471
When the network is plugged 0.028
And Tor is ready 13.144
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.227
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.671
Given I shutdown Tails and wait for the computer to power off 9.810
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:9.579
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 5.386
And the file system changes introduced in version 6.2~testoverlayfs are present 0.301
And only the 6.2~testoverlayfs SquashFS delta is installed 0.047
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.160
# 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.295
When the network is plugged 0.016
And Tor is ready 9.933
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.008
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.214
Given I shutdown Tails and wait for the computer to power off 8.627
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.092
Then Tails is running version 6.3~testoverlayfs 0.008
And all tps features are active 5.530
And the file system changes introduced in version 6.3~testoverlayfs are present 0.374
And only the 6.3~testoverlayfs SquashFS delta is installed 0.052
# 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.180
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.211
When the network is plugged 0.017
And Tor is ready 10.687
Then the Upgrader considers the system as up-to-date 10.546
# 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.287
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.455
After features/support/hooks.rb:339 0.990
After features/support/hooks.rb:108 0.054
Tags: @product @automatic_upgrade
21.489
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.020
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.954
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.227
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the signing key used by the Upgrader is outdated 0.055
But a current signing key is available on our website 0.000
When the network is plugged 0.019
And Tor is ready 10.150
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.028
After features/support/hooks.rb:339 0.852
After features/support/hooks.rb:108 0.000