Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 39 22 May 2026, 14:38

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:6.297 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:14.751
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.078
And I create a 7200 MiB disk named "old" 0.014
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 14.454
When I start Tails from USB drive "old" with network unplugged 55.061
Then the boot device has safe access rights 3.166
And Tails is running from USB drive "old" 0.342
And there is no persistence partition on USB drive "old" 0.056
And process "udev-watchdog" is running 0.070
And udev-watchdog is monitoring the correct device 0.262
And I unplug USB drive "old" 0.223
After features/support/hooks.rb:335 1.687
After features/support/hooks.rb:104 0.008
Tags: @product
1:34.308
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.092
And I start Tails from USB drive "old" with network unplugged and I login 58.968
Then Tails is running from USB drive "old" 0.383
And I create a persistent partition 26.351
And I take note of which tps features are available 0.402
Then a Tails persistence partition exists on USB drive "old" 0.834
And I shutdown Tails and wait for the computer to power off 7.276
After features/support/hooks.rb:335 0.543
After features/support/hooks.rb:104 0.009
Tags: @product
1:34.200
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.003
Given a computer 0.065
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:7.473
Then Tails is running from USB drive "old" 0.291
And all tps features are active 1.212
When I write some files expected to persist 1.374
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.185
And all persistence configuration files have safe access rights 0.349
And all persistent directories from the old Tails version have safe access rights 2.094
And I take note of which tps features are available 0.160
And I shutdown Tails and wait for the computer to power off 8.325
# 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.667
After features/support/hooks.rb:335 0.169
After features/support/hooks.rb:104 0.007
Tags: @product
2:16.651
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 9.217
And I log in to a new session 14.691
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.885
And I plug USB drive "to_upgrade" 2.261
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.833
Then the running Tails is installed on USB drive "to_upgrade" 16.487
And I unplug USB drive "to_upgrade" 0.134
And I unplug USB drive "__internal" 0.139
After features/support/hooks.rb:335 2.135
After features/support/hooks.rb:104 0.000
Tags: @product
1:13.074
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.092
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.081
Then all tps features from the old Tails version are active 1.127
And Tails is running from USB drive "to_upgrade" 0.308
And the boot device has safe access rights 3.150
And the expected persistent files created with the old Tails version are present in the filesystem 1.318
And all persistent directories from the old Tails version have safe access rights 1.995
After features/support/hooks.rb:335 0.767
After features/support/hooks.rb:104 0.007
3:52.596
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.147
And no SquashFS delta is installed 0.176
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.060
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.257
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.421
When the network is plugged 0.016
And Tor is ready 14.608
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.796
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.141
Given I shutdown Tails and wait for the computer to power off 8.518
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.608
Then Tails is running version 6.2~testoverlayfs 0.033
And all tps features are active 1.302
And the file system changes introduced in version 6.2~testoverlayfs are present 0.279
And only the 6.2~testoverlayfs SquashFS delta is installed 0.053
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.149
# 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.216
When the network is plugged 0.015
And Tor is ready 9.999
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.413
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 6.171
Given I shutdown Tails and wait for the computer to power off 8.636
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.784
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.250
And the file system changes introduced in version 6.3~testoverlayfs are present 0.428
And only the 6.3~testoverlayfs SquashFS delta is installed 0.050
# 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.152
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.219
When the network is plugged 0.018
And Tor is ready 11.604
Then the Upgrader considers the system as up-to-date 10.550
# 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.764
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.478
After features/support/hooks.rb:335 0.913
After features/support/hooks.rb:104 0.019
20.714
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.006
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.805
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.231
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.043
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 8.923
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.650
After features/support/hooks.rb:335 1.125
After features/support/hooks.rb:104 0.000