Project Number Date
test_Tails_ISO_21565-flatpak-safe 48 23 Sep 2026, 16:21

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 61 1 25 0 0 87 6 1 7 37:34.295 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:18.636
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.084
And I create a 7200 MiB disk named "old" 0.021
And I plug USB drive "old" 1.021
And I write an old version of the Tails USB image to disk "old" 13.937
When I start Tails from USB drive "old" with network unplugged 1:0.412
Then the boot device has safe access rights 2.514
And Tails is running from USB drive "old" 0.222
And there is no persistence partition on USB drive "old" 0.057
And process "udev-watchdog" is running 0.051
And udev-watchdog is monitoring the correct device 0.200
And I unplug USB drive "old" 0.112
After features/support/hooks.rb:339 3.424
After features/support/hooks.rb:108 0.019
Tags: @product
1:25.895
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.089
And I start Tails from USB drive "old" with network unplugged and I login 50.450
Then Tails is running from USB drive "old" 0.280
And I create a persistent partition 24.438
And I take note of which tps features are available 6.288
Then a Tails persistence partition exists on USB drive "old" 0.512
And I shutdown Tails and wait for the computer to power off 3.836
After features/support/hooks.rb:339 0.422
After features/support/hooks.rb:108 0.005
Tags: @product
1:36.307
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Given a computer 0.096
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.966
Then Tails is running from USB drive "old" 0.229
And all tps features are active 7.541
When I write some files expected to persist 1.056
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.140
And all persistence configuration files have safe access rights 0.238
And all persistent directories from the old Tails version have safe access rights 1.761
And I take note of which tps features are available 6.492
And I shutdown Tails and wait for the computer to power off 2.660
# 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.124
After features/support/hooks.rb:339 0.525
After features/support/hooks.rb:108 0.007
Tags: @product
2:15.171
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.948
And I log in to a new session 11.635
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.876
And I plug USB drive "to_upgrade" 2.202
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.795
Then the running Tails is installed on USB drive "to_upgrade" 19.462
And I unplug USB drive "to_upgrade" 0.126
And I unplug USB drive "__internal" 0.124
After features/support/hooks.rb:339 0.634
After features/support/hooks.rb:108 0.000
Tags: @product
1:11.703
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.090
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.311
Then all tps features from the old Tails version are active 1.282
And Tails is running from USB drive "to_upgrade" 0.209
And the boot device has safe access rights 2.832
And the expected persistent files created with the old Tails version are present in the filesystem 1.147
And all persistent directories from the old Tails version have safe access rights 1.829
After features/support/hooks.rb:339 0.592
After features/support/hooks.rb:108 0.013
Tags: @product @automatic_upgrade
29:19.187
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.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.418
And no SquashFS delta is installed 0.098
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.199
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.064
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.216
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.368
When the network is plugged 0.036
And Tor is ready 12.723
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.556
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 28:55.505
Tor 
Tor operation failed (despite retrying 10 times) with
FindFailed: can not find any of the patterns ["TailsUpgraderDownloadComplete.png", "TailsUpgraderFailure.png"] on the screen (MaxRetriesFailure)
./features/support/helpers/misc_helpers.rb:226:in `rescue in block in retry_action'
./features/support/helpers/misc_helpers.rb:209:in `block in retry_action'
<internal:kernel>:187:in `loop'
./features/support/helpers/misc_helpers.rb:208:in `retry_action'
./features/support/helpers/misc_helpers.rb:196:in `retry_tor'
./features/step_definitions/usb.rb:1362:in `/^I can successfully install the incremental upgrade to version (.+)$/'
features/usb_upgrade.feature:91:in `And I can successfully install the incremental upgrade to version 6.2~testoverlayfs'
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
Then Tails is running version 6.2~testoverlayfs 0.000
And all tps features are active 0.000
And the file system changes introduced in version 6.2~testoverlayfs are present 0.000
And only the 6.2~testoverlayfs SquashFS delta is installed 0.000
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.000
# 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.000
When the network is plugged 0.000
And Tor is ready 0.000
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 0.000
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 0.000
Given I shutdown Tails and wait for the computer to power off 0.000
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 0.000
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 5.031 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:46:45)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/48/artifact/build-artifacts/01:46:45_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/48/artifact/build-artifacts/01:46:45_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/48/artifact/build-artifacts/01:46:45_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/48/artifact/build-artifacts/01:46:45_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:108 0.000
Tags: @product @automatic_upgrade
27.392
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 with a persistent partition enabled and logged in 7.664
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.221
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.065
And the signing key used by the Upgrader is outdated 0.055
But a current signing key is available on our website 0.000
When the network is plugged 0.032
And Tor is ready 9.004
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 10.348
After features/support/hooks.rb:339 1.069
After features/support/hooks.rb:108 0.000