Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 26 13 May 2026, 20:24

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:54.013 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:19.061
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.050
And I create a 7200 MiB disk named "old" 0.011
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.035
When I start Tails from USB drive "old" with network unplugged 1:1.246
Then the boot device has safe access rights 2.983
And Tails is running from USB drive "old" 0.235
And there is no persistence partition on USB drive "old" 0.054
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.200
And I unplug USB drive "old" 0.176
After features/support/hooks.rb:335 3.569
After features/support/hooks.rb:104 0.046
Tags: @product
1:29.539
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.076
And I start Tails from USB drive "old" with network unplugged and I login 54.131
Then Tails is running from USB drive "old" 0.297
And I create a persistent partition 25.752
And I take note of which tps features are available 0.384
Then a Tails persistence partition exists on USB drive "old" 0.621
And I shutdown Tails and wait for the computer to power off 8.275
After features/support/hooks.rb:335 0.353
After features/support/hooks.rb:104 0.007
Tags: @product
1:29.842
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.058
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.132
Then Tails is running from USB drive "old" 0.282
And all tps features are active 1.233
When I write some files expected to persist 1.421
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.227
And all persistence configuration files have safe access rights 0.376
And all persistent directories from the old Tails version have safe access rights 2.151
And I take note of which tps features are available 0.168
And I shutdown Tails and wait for the computer to power off 8.369
# 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.419
After features/support/hooks.rb:335 0.524
After features/support/hooks.rb:104 0.007
Tags: @product
2:13.661
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.747
And I log in to a new session 13.794
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.997
And I plug USB drive "to_upgrade" 2.238
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.019
Then the running Tails is installed on USB drive "to_upgrade" 16.468
And I unplug USB drive "to_upgrade" 0.230
And I unplug USB drive "__internal" 0.163
After features/support/hooks.rb:335 2.399
After features/support/hooks.rb:104 0.000
Tags: @product
1:11.471
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.066
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.319
Then all tps features from the old Tails version are active 1.155
And Tails is running from USB drive "to_upgrade" 0.241
And the boot device has safe access rights 2.673
And the expected persistent files created with the old Tails version are present in the filesystem 1.189
And all persistent directories from the old Tails version have safe access rights 1.825
After features/support/hooks.rb:335 0.810
After features/support/hooks.rb:104 0.039
Tags: @product @automatic_upgrade
3:49.524
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.395
And no SquashFS delta is installed 0.069
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.281
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.344
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.425
When the network is plugged 0.014
And Tor is ready 14.293
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.866
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.207
Given I shutdown Tails and wait for the computer to power off 9.523
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.720
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.319
And the file system changes introduced in version 6.2~testoverlayfs are present 0.270
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.164
# 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.246
When the network is plugged 0.025
And Tor is ready 11.038
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 2.542
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.234
Given I shutdown Tails and wait for the computer to power off 8.274
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.664
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.206
And the file system changes introduced in version 6.3~testoverlayfs are present 0.362
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.221
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.214
When the network is plugged 0.014
And Tor is ready 11.497
Then the Upgrader considers the system as up-to-date 10.748
# 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.814
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.364
After features/support/hooks.rb:335 1.074
After features/support/hooks.rb:104 0.055
Tags: @product @automatic_upgrade
20.913
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 7.475
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.225
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the signing key used by the Upgrader is outdated 0.045
But a current signing key is available on our website 0.000
When the network is plugged 0.018
And Tor is ready 9.702
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.401
After features/support/hooks.rb:335 0.922
After features/support/hooks.rb:104 0.000