Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 56 09 Jun 2026, 18:04

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.080 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.282
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.052
And I create a 7200 MiB disk named "old" 0.008
And I plug USB drive "old" 1.016
And I write an old version of the Tails USB image to disk "old" 13.935
When I start Tails from USB drive "old" with network unplugged 55.664
Then the boot device has safe access rights 2.866
And Tails is running from USB drive "old" 0.263
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.067
And udev-watchdog is monitoring the correct device 0.238
And I unplug USB drive "old" 0.126
After features/support/hooks.rb:335 3.805
After features/support/hooks.rb:104 0.014
Tags: @product
1:29.280
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.053
And I start Tails from USB drive "old" with network unplugged and I login 55.034
Then Tails is running from USB drive "old" 0.277
And I create a persistent partition 24.996
And I take note of which tps features are available 0.341
Then a Tails persistence partition exists on USB drive "old" 0.496
And I shutdown Tails and wait for the computer to power off 8.079
After features/support/hooks.rb:335 0.606
After features/support/hooks.rb:104 0.007
Tags: @product
1:28.263
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.075
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.264
Then Tails is running from USB drive "old" 0.274
And all tps features are active 1.172
When I write some files expected to persist 1.319
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.155
And all persistence configuration files have safe access rights 0.340
And all persistent directories from the old Tails version have safe access rights 1.914
And I take note of which tps features are available 0.146
And I shutdown Tails and wait for the computer to power off 8.009
# 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.592
After features/support/hooks.rb:335 0.559
After features/support/hooks.rb:104 0.007
Tags: @product
2:11.506
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 8.363
And I log in to a new session 12.825
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.684
And I plug USB drive "to_upgrade" 2.239
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.789
Then the running Tails is installed on USB drive "to_upgrade" 15.287
And I unplug USB drive "to_upgrade" 0.176
And I unplug USB drive "__internal" 0.140
After features/support/hooks.rb:335 2.368
After features/support/hooks.rb:104 0.000
Tags: @product
1:9.267
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.054
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:2.447
Then all tps features from the old Tails version are active 0.987
And Tails is running from USB drive "to_upgrade" 0.313
And the boot device has safe access rights 2.306
And the expected persistent files created with the old Tails version are present in the filesystem 1.125
And all persistent directories from the old Tails version have safe access rights 2.032
After features/support/hooks.rb:335 1.103
After features/support/hooks.rb:104 0.007
Tags: @product @automatic_upgrade
3:47.040
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.127
And no SquashFS delta is installed 0.063
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.261
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.053
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.268
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.465
When the network is plugged 0.017
And Tor is ready 12.339
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.828
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.909
Given I shutdown Tails and wait for the computer to power off 9.879
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.819
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.337
And the file system changes introduced in version 6.2~testoverlayfs are present 0.210
And only the 6.2~testoverlayfs SquashFS delta is installed 0.063
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.134
# 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.212
When the network is plugged 0.018
And Tor is ready 10.121
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.254
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.390
Given I shutdown Tails and wait for the computer to power off 8.016
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:2.933
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 1.280
And the file system changes introduced in version 6.3~testoverlayfs are present 0.444
And only the 6.3~testoverlayfs SquashFS delta is installed 0.065
# 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.218
When the network is plugged 0.014
And Tor is ready 11.324
Then the Upgrader considers the system as up-to-date 10.630
# 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.833
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.348
After features/support/hooks.rb:335 0.932
After features/support/hooks.rb:104 0.016
Tags: @product @automatic_upgrade
21.438
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 7.624
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.183
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.047
And the signing key used by the Upgrader is outdated 0.040
But a current signing key is available on our website 0.000
When the network is plugged 0.014
And Tor is ready 9.847
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.680
After features/support/hooks.rb:335 0.793
After features/support/hooks.rb:104 0.000