Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 34 19 May 2026, 19:42

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:55.542 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:13.140
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.060
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.747
When I start Tails from USB drive "old" with network unplugged 54.277
Then the boot device has safe access rights 3.281
And Tails is running from USB drive "old" 0.280
And there is no persistence partition on USB drive "old" 0.051
And process "udev-watchdog" is running 0.057
And udev-watchdog is monitoring the correct device 0.212
And I unplug USB drive "old" 0.147
After features/support/hooks.rb:335 3.623
After features/support/hooks.rb:104 0.007
Tags: @product
1:32.107
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.062
And I start Tails from USB drive "old" with network unplugged and I login 56.719
Then Tails is running from USB drive "old" 0.255
And I create a persistent partition 25.724
And I take note of which tps features are available 0.383
Then a Tails persistence partition exists on USB drive "old" 0.553
And I shutdown Tails and wait for the computer to power off 8.410
After features/support/hooks.rb:335 0.340
After features/support/hooks.rb:104 0.009
Tags: @product
1:31.493
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.082
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:4.755
Then Tails is running from USB drive "old" 0.294
And all tps features are active 1.500
When I write some files expected to persist 1.450
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.191
And all persistence configuration files have safe access rights 0.337
And all persistent directories from the old Tails version have safe access rights 1.930
And I take note of which tps features are available 0.154
And I shutdown Tails and wait for the computer to power off 7.943
# 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.852
After features/support/hooks.rb:335 0.349
After features/support/hooks.rb:104 0.008
Tags: @product
2:14.371
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 without a persistent partition and stopped at Tails Greeter's login screen 8.034
And I log in to a new session 14.443
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.833
And I plug USB drive "to_upgrade" 2.233
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.464
Then the running Tails is installed on USB drive "to_upgrade" 15.998
And I unplug USB drive "to_upgrade" 0.174
And I unplug USB drive "__internal" 0.188
After features/support/hooks.rb:335 2.349
After features/support/hooks.rb:104 0.000
Tags: @product
1:14.187
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.058
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.967
Then all tps features from the old Tails version are active 1.132
And Tails is running from USB drive "to_upgrade" 0.248
And the boot device has safe access rights 2.751
And the expected persistent files created with the old Tails version are present in the filesystem 1.554
And all persistent directories from the old Tails version have safe access rights 2.474
After features/support/hooks.rb:335 0.559
After features/support/hooks.rb:104 0.023
Tags: @product @automatic_upgrade
3:49.615
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.372
And no SquashFS delta is installed 0.053
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.047
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.219
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.361
When the network is plugged 0.015
And Tor is ready 13.835
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.978
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.453
Given I shutdown Tails and wait for the computer to power off 5.788
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:10.371
Then Tails is running version 6.2~testoverlayfs 0.005
And all tps features are active 1.348
And the file system changes introduced in version 6.2~testoverlayfs are present 0.229
And only the 6.2~testoverlayfs SquashFS delta is installed 0.052
# 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.226
When the network is plugged 0.019
And Tor is ready 10.730
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 3.004
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.617
Given I shutdown Tails and wait for the computer to power off 8.151
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.339
Then Tails is running version 6.3~testoverlayfs 0.006
And all tps features are active 1.270
And the file system changes introduced in version 6.3~testoverlayfs are present 0.410
And only the 6.3~testoverlayfs SquashFS delta is installed 0.058
# 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.169
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.250
When the network is plugged 0.017
And Tor is ready 10.320
Then the Upgrader considers the system as up-to-date 10.722
# 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.415
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.381
After features/support/hooks.rb:335 0.852
After features/support/hooks.rb:104 0.014
Tags: @product @automatic_upgrade
20.625
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.011
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.697
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.262
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.075
And the signing key used by the Upgrader is outdated 0.076
But a current signing key is available on our website 0.000
When the network is plugged 0.047
And Tor is ready 10.422
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.042
After features/support/hooks.rb:335 0.707
After features/support/hooks.rb:104 0.000