Project Number Date
test_Tails_ISO_21584-yelp-flatpak-sandbox-escape 1 18 May 2026, 18:03

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:11.554 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:8.240
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.053
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 12.779
When I start Tails from USB drive "old" with network unplugged 51.278
Then the boot device has safe access rights 2.457
And Tails is running from USB drive "old" 0.212
And there is no persistence partition on USB drive "old" 0.038
And process "udev-watchdog" is running 0.052
And udev-watchdog is monitoring the correct device 0.203
And I unplug USB drive "old" 0.135
After features/support/hooks.rb:335 1.321
After features/support/hooks.rb:104 0.006
Tags: @product
1:25.071
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.050
And I start Tails from USB drive "old" with network unplugged and I login 52.414
Then Tails is running from USB drive "old" 0.227
And I create a persistent partition 23.616
And I take note of which tps features are available 0.328
Then a Tails persistence partition exists on USB drive "old" 0.530
And I shutdown Tails and wait for the computer to power off 7.904
After features/support/hooks.rb:335 0.251
After features/support/hooks.rb:104 0.007
Tags: @product
1:26.226
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.048
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.210
Then Tails is running from USB drive "old" 0.263
And all tps features are active 1.289
When I write some files expected to persist 1.365
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.162
And all persistence configuration files have safe access rights 0.279
And all persistent directories from the old Tails version have safe access rights 1.809
And I take note of which tps features are available 0.151
And I shutdown Tails and wait for the computer to power off 7.839
# 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.806
After features/support/hooks.rb:335 0.598
After features/support/hooks.rb:104 0.007
Tags: @product
2:9.934
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 without a persistent partition and stopped at Tails Greeter's login screen 7.419
And I log in to a new session 12.490
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.657
And I plug USB drive "to_upgrade" 2.218
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.471
Then the running Tails is installed on USB drive "to_upgrade" 15.399
And I unplug USB drive "to_upgrade" 0.137
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:335 2.116
After features/support/hooks.rb:104 0.000
Tags: @product
1:6.915
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.051
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 59.852
Then all tps features from the old Tails version are active 1.018
And Tails is running from USB drive "to_upgrade" 0.227
And the boot device has safe access rights 2.606
And the expected persistent files created with the old Tails version are present in the filesystem 1.136
And all persistent directories from the old Tails version have safe access rights 2.022
After features/support/hooks.rb:335 0.805
After features/support/hooks.rb:104 0.006
Tags: @product @automatic_upgrade
3:34.572
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.128
And no SquashFS delta is installed 0.049
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.208
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.040
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.232
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.313
When the network is plugged 0.013
And Tor is ready 13.449
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.799
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.314
Given I shutdown Tails and wait for the computer to power off 11.062
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:1.705
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.039
And the file system changes introduced in version 6.2~testoverlayfs are present 0.206
And only the 6.2~testoverlayfs SquashFS delta is installed 0.044
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.145
# 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.208
When the network is plugged 0.016
And Tor is ready 10.557
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.915
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.355
Given I shutdown Tails and wait for the computer to power off 7.916
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 58.655
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.081
And the file system changes introduced in version 6.3~testoverlayfs are present 0.354
And only the 6.3~testoverlayfs SquashFS delta is installed 0.039
# 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.144
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.183
When the network is plugged 0.012
And Tor is ready 10.656
Then the Upgrader considers the system as up-to-date 10.530
# 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.798
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.382
After features/support/hooks.rb:335 0.992
After features/support/hooks.rb:104 0.011
Tags: @product @automatic_upgrade
20.594
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 7.435
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.217
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the signing key used by the Upgrader is outdated 0.050
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 9.670
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.166
After features/support/hooks.rb:335 0.648
After features/support/hooks.rb:104 0.000