Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 28 15 May 2026, 14:25

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:40.009 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:6.238
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Given a computer 0.062
And I create a 7200 MiB disk named "old" 0.010
And I plug USB drive "old" 1.029
And I write an old version of the Tails USB image to disk "old" 13.203
When I start Tails from USB drive "old" with network unplugged 48.005
Then the boot device has safe access rights 3.168
And Tails is running from USB drive "old" 0.239
And there is no persistence partition on USB drive "old" 0.053
And process "udev-watchdog" is running 0.080
And udev-watchdog is monitoring the correct device 0.242
And I unplug USB drive "old" 0.143
After features/support/hooks.rb:335 3.854
After features/support/hooks.rb:104 0.006
Tags: @product
1:30.125
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.001
Given a computer 0.069
And I start Tails from USB drive "old" with network unplugged and I login 55.352
Then Tails is running from USB drive "old" 0.274
And I create a persistent partition 25.141
And I take note of which tps features are available 0.371
Then a Tails persistence partition exists on USB drive "old" 0.527
And I shutdown Tails and wait for the computer to power off 8.387
After features/support/hooks.rb:335 0.217
After features/support/hooks.rb:104 0.010
Tags: @product
1:30.598
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.005
Given a computer 0.060
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.953
Then Tails is running from USB drive "old" 0.276
And all tps features are active 1.261
When I write some files expected to persist 1.410
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.208
And all persistence configuration files have safe access rights 0.346
And all persistent directories from the old Tails version have safe access rights 2.120
And I take note of which tps features are available 0.163
And I shutdown Tails and wait for the computer to power off 8.323
# 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.473
After features/support/hooks.rb:335 0.231
After features/support/hooks.rb:104 0.007
Tags: @product
2:12.131
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.557
And I log in to a new session 13.118
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.794
And I plug USB drive "to_upgrade" 2.227
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:32.381
Then the running Tails is installed on USB drive "to_upgrade" 15.746
And I unplug USB drive "to_upgrade" 0.160
And I unplug USB drive "__internal" 0.144
After features/support/hooks.rb:335 0.715
After features/support/hooks.rb:104 0.000
Tags: @product
1:11.764
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given a computer 0.069
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.445
Then all tps features from the old Tails version are active 1.176
And Tails is running from USB drive "to_upgrade" 0.246
And the boot device has safe access rights 2.627
And the expected persistent files created with the old Tails version are present in the filesystem 1.111
And all persistent directories from the old Tails version have safe access rights 2.086
After features/support/hooks.rb:335 1.036
After features/support/hooks.rb:104 0.007
Tags: @product @automatic_upgrade
3:47.308
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.196
And no SquashFS delta is installed 0.062
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.287
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.051
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.275
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.405
When the network is plugged 0.014
And Tor is ready 12.518
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 3.473
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.868
Given I shutdown Tails and wait for the computer to power off 9.482
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:6.584
Then Tails is running version 6.2~testoverlayfs 0.006
And all tps features are active 1.248
And the file system changes introduced in version 6.2~testoverlayfs are present 0.284
And only the 6.2~testoverlayfs SquashFS delta is installed 0.095
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.183
# 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.189
When the network is plugged 0.013
And Tor is ready 11.373
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.114
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 5.735
Given I shutdown Tails and wait for the computer to power off 8.242
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:3.028
Then Tails is running version 6.3~testoverlayfs 0.007
And all tps features are active 1.235
And the file system changes introduced in version 6.3~testoverlayfs are present 0.423
And only the 6.3~testoverlayfs SquashFS delta is installed 0.048
# 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.153
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.239
When the network is plugged 0.018
And Tor is ready 10.455
Then the Upgrader considers the system as up-to-date 10.628
# 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.888
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.474
After features/support/hooks.rb:335 0.767
After features/support/hooks.rb:104 0.017
Tags: @product @automatic_upgrade
21.842
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.491
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.278
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.054
But a current signing key is available on our website 0.000
When the network is plugged 0.015
And Tor is ready 11.076
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2.881
After features/support/hooks.rb:335 0.972
After features/support/hooks.rb:104 0.000