Project Number Date
test_Tails_ISO_21565-flatpak-safe 68 05 Oct 2026, 16:28

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 75 1 11 0 0 87 6 1 7 11:6.102 Failed
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:24.957
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.091
And I create a 7200 MiB disk named "old" 0.024
And I plug USB drive "old" 1.019
And I write an old version of the Tails USB image to disk "old" 13.679
When I start Tails from USB drive "old" with network unplugged 1:6.462
Then the boot device has safe access rights 2.976
And Tails is running from USB drive "old" 0.237
And there is no persistence partition on USB drive "old" 0.042
And process "udev-watchdog" is running 0.060
And udev-watchdog is monitoring the correct device 0.208
And I unplug USB drive "old" 0.154
After features/support/hooks.rb:339 1.254
After features/support/hooks.rb:108 0.006
Tags: @product
1:29.131
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.110
And I start Tails from USB drive "old" with network unplugged and I login 50.862
Then Tails is running from USB drive "old" 0.277
And I create a persistent partition 25.047
And I take note of which tps features are available 7.012
Then a Tails persistence partition exists on USB drive "old" 0.516
And I shutdown Tails and wait for the computer to power off 5.304
After features/support/hooks.rb:339 0.244
After features/support/hooks.rb:108 0.005
Tags: @product
1:35.317
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.087
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:2.029
Then Tails is running from USB drive "old" 0.303
And all tps features are active 8.757
When I write some files expected to persist 1.428
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.197
And all persistence configuration files have safe access rights 0.322
And all persistent directories from the old Tails version have safe access rights 1.778
And I take note of which tps features are available 5.863
And I shutdown Tails and wait for the computer to power off 2.559
# 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" 11.988
After features/support/hooks.rb:339 0.485
After features/support/hooks.rb:108 0.006
Tags: @product
2:14.614
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 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.449
And I log in to a new session 12.913
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.818
And I plug USB drive "to_upgrade" 2.230
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.796
Then the running Tails is installed on USB drive "to_upgrade" 18.156
And I unplug USB drive "to_upgrade" 0.131
And I unplug USB drive "__internal" 0.118
After features/support/hooks.rb:339 2.074
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.143
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.015
Given a computer 0.082
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:3.986
Then all tps features from the old Tails version are active 1.081
And Tails is running from USB drive "to_upgrade" 0.207
And the boot device has safe access rights 2.051
And the expected persistent files created with the old Tails version are present in the filesystem 0.961
And all persistent directories from the old Tails version have safe access rights 1.772
After features/support/hooks.rb:339 0.539
After features/support/hooks.rb:108 0.029
Tags: @product @automatic_upgrade
2:52.711
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.500
And no SquashFS delta is installed 0.070
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.193
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.039
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.184
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.300
When the network is plugged 0.032
And Tor is ready 12.164
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.923
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 6.567
Given I shutdown Tails and wait for the computer to power off 5.534
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:8.683
Then Tails is running version 6.2~testoverlayfs 0.004
And all tps features are active 10.365
And the file system changes introduced in version 6.2~testoverlayfs are present 0.275
And only the 6.2~testoverlayfs SquashFS delta is installed 0.046
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.116
# 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.197
When the network is plugged 0.043
And Tor is ready 10.471
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.050
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.840
Given I shutdown Tails and wait for the computer to power off 4.110
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 37.991
Known 
Known issue #20282: Error starting GDM with your graphics card (RuntimeError)
./features/step_definitions/common_steps.rb:450:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:238:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/usb_upgrade.feature:109:in `When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
Then Tails is running version 6.3~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present 0.000
And only the 6.3~testoverlayfs SquashFS delta is installed 0.000
# 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.000
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.000
When the network is plugged 0.000
And Tor is ready 0.000
Then the Upgrader considers the system as up-to-date 0.000
# 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 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.000
After features/support/hooks.rb:339 4.799 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:20:19)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/68/artifact/build-artifacts/01:20:19_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/68/artifact/build-artifacts/01:20:19_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/68/artifact/build-artifacts/01:20:19_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/68/artifact/build-artifacts/01:20:19_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:108 0.017
Tags: @product @automatic_upgrade
19.226
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.317
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.256
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.043
And the signing key used by the Upgrader is outdated 0.066
But a current signing key is available on our website 0.000
When the network is plugged 0.040
And Tor is ready 9.668
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 0.832
After features/support/hooks.rb:339 0.941
After features/support/hooks.rb:108 0.000