Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 51 05 Jun 2026, 14:28

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:41.090 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:22.319
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.061
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.015
And I write an old version of the Tails USB image to disk "old" 13.563
When I start Tails from USB drive "old" with network unplugged 1:4.460
Then the boot device has safe access rights 2.521
And Tails is running from USB drive "old" 0.235
And there is no persistence partition on USB drive "old" 0.040
And process "udev-watchdog" is running 0.048
And udev-watchdog is monitoring the correct device 0.224
And I unplug USB drive "old" 0.139
After features/support/hooks.rb:335 3.969
After features/support/hooks.rb:104 0.006
Tags: @product
1:27.845
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 55.016
Then Tails is running from USB drive "old" 0.257
And I create a persistent partition 26.566
And I take note of which tps features are available 0.428
Then a Tails persistence partition exists on USB drive "old" 0.839
And I shutdown Tails and wait for the computer to power off 4.686
After features/support/hooks.rb:335 0.544
After features/support/hooks.rb:104 0.007
Tags: @product
1:28.118
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.061
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:1.930
Then Tails is running from USB drive "old" 0.263
And all tps features are active 1.301
When I write some files expected to persist 1.332
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.156
And all persistence configuration files have safe access rights 0.326
And all persistent directories from the old Tails version have safe access rights 1.848
And I take note of which tps features are available 0.148
And I shutdown Tails and wait for the computer to power off 8.306
# 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.443
After features/support/hooks.rb:335 0.181
After features/support/hooks.rb:104 0.006
Tags: @product
2:10.198
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 8.164
And I log in to a new session 11.883
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.756
And I plug USB drive "to_upgrade" 2.229
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.453
Then the running Tails is installed on USB drive "to_upgrade" 15.403
And I unplug USB drive "to_upgrade" 0.165
And I unplug USB drive "__internal" 0.141
After features/support/hooks.rb:335 0.712
After features/support/hooks.rb:104 0.000
Tags: @product
1:9.938
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.079
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.071
Then all tps features from the old Tails version are active 1.054
And Tails is running from USB drive "to_upgrade" 0.239
And the boot device has safe access rights 2.554
And the expected persistent files created with the old Tails version are present in the filesystem 1.129
And all persistent directories from the old Tails version have safe access rights 1.809
After features/support/hooks.rb:335 0.840
After features/support/hooks.rb:104 0.008
Tags: @product @automatic_upgrade
3:42.850
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.033
And no SquashFS delta is installed 0.083
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.222
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.045
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.225
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.432
When the network is plugged 0.022
And Tor is ready 13.448
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.971
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.189
Given I shutdown Tails and wait for the computer to power off 9.390
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:4.941
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.385
And the file system changes introduced in version 6.2~testoverlayfs are present 0.263
And only the 6.2~testoverlayfs SquashFS delta is installed 0.049
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.155
# 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.252
When the network is plugged 0.017
And Tor is ready 9.884
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.349
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.589
Given I shutdown Tails and wait for the computer to power off 4.277
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.189
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.066
And the file system changes introduced in version 6.3~testoverlayfs are present 0.351
And only the 6.3~testoverlayfs SquashFS delta is installed 0.067
# 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.199
When the network is plugged 0.017
And Tor is ready 11.380
Then the Upgrader considers the system as up-to-date 10.529
# 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.241
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.419
After features/support/hooks.rb:335 1.397
After features/support/hooks.rb:104 0.017
Tags: @product @automatic_upgrade
19.819
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 7.554
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.040
And the signing key used by the Upgrader is outdated 0.052
But a current signing key is available on our website 0.000
When the network is plugged 0.020
And Tor is ready 10.625
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.310
After features/support/hooks.rb:335 1.008
After features/support/hooks.rb:104 0.000