Project Number Date
test_Tails_ISO_21584-yelp-flatpak-sandbox-escape 2 18 May 2026, 22:05

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:1.858 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:6.494
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.007
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 12.734
When I start Tails from USB drive "old" with network unplugged 49.258
Then the boot device has safe access rights 2.740
And Tails is running from USB drive "old" 0.210
And there is no persistence partition on USB drive "old" 0.043
And process "udev-watchdog" is running 0.073
And udev-watchdog is monitoring the correct device 0.201
And I unplug USB drive "old" 0.156
After features/support/hooks.rb:335 1.564
After features/support/hooks.rb:104 0.006
Tags: @product
1:26.569
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login 52.648
Then Tails is running from USB drive "old" 0.250
And I create a persistent partition 24.608
And I take note of which tps features are available 0.383
Then a Tails persistence partition exists on USB drive "old" 0.545
And I shutdown Tails and wait for the computer to power off 8.080
After features/support/hooks.rb:335 0.449
After features/support/hooks.rb:104 0.008
Tags: @product
1:21.110
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.071
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.990
Then Tails is running from USB drive "old" 0.214
And all tps features are active 1.309
When I write some files expected to persist 1.328
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.182
And all persistence configuration files have safe access rights 0.295
And all persistent directories from the old Tails version have safe access rights 1.735
And I take note of which tps features are available 0.147
And I shutdown Tails and wait for the computer to power off 4.061
# 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.774
After features/support/hooks.rb:335 0.188
After features/support/hooks.rb:104 0.006
Tags: @product
2:7.780
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 without a persistent partition and stopped at Tails Greeter's login screen 7.689
And I log in to a new session 11.528
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.762
And I plug USB drive "to_upgrade" 2.207
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.363
Then the running Tails is installed on USB drive "to_upgrade" 13.947
And I unplug USB drive "to_upgrade" 0.142
And I unplug USB drive "__internal" 0.137
After features/support/hooks.rb:335 1.938
After features/support/hooks.rb:104 0.000
Tags: @product
1:7.017
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.979
Then all tps features from the old Tails version are active 0.935
And Tails is running from USB drive "to_upgrade" 0.224
And the boot device has safe access rights 2.702
And the expected persistent files created with the old Tails version are present in the filesystem 1.219
And all persistent directories from the old Tails version have safe access rights 1.903
After features/support/hooks.rb:335 0.677
After features/support/hooks.rb:104 0.007
Tags: @product @automatic_upgrade
3:33.481
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.195
And no SquashFS delta is installed 0.060
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.224
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.042
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.306
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.345
When the network is plugged 0.013
And Tor is ready 12.135
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.161
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 4.399
Given I shutdown Tails and wait for the computer to power off 6.773
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.081
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.065
And the file system changes introduced in version 6.2~testoverlayfs are present 0.236
And only the 6.2~testoverlayfs SquashFS delta is installed 0.100
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.135
# 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.020
And Tor is ready 10.067
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.144
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.550
Given I shutdown Tails and wait for the computer to power off 7.936
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 59.554
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 0.985
And the file system changes introduced in version 6.3~testoverlayfs are present 0.346
And only the 6.3~testoverlayfs SquashFS delta is installed 0.046
# 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.141
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.182
When the network is plugged 0.018
And Tor is ready 10.931
Then the Upgrader considers the system as up-to-date 10.513
# 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.138
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.407
After features/support/hooks.rb:335 0.911
After features/support/hooks.rb:104 0.023
Tags: @product @automatic_upgrade
19.404
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.015
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.698
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.044
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.019
And Tor is ready 9.650
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.725
After features/support/hooks.rb:335 0.816
After features/support/hooks.rb:104 0.000