Project Number Date
test_Tails_ISO_21565-flatpak-safe 47 23 Sep 2026, 16:09

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 50:21.859 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:4.760
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.086
And I create a 7200 MiB disk named "old" 0.023
And I plug USB drive "old" 1.026
And I write an old version of the Tails USB image to disk "old" 13.663
When I start Tails from USB drive "old" with network unplugged 47.231
Then the boot device has safe access rights 2.039
And Tails is running from USB drive "old" 0.237
And there is no persistence partition on USB drive "old" 0.052
And process "udev-watchdog" is running 0.049
And udev-watchdog is monitoring the correct device 0.211
And I unplug USB drive "old" 0.137
After features/support/hooks.rb:339 1.523
After features/support/hooks.rb:108 0.006
Tags: @product
1:24.410
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.123
And I start Tails from USB drive "old" with network unplugged and I login 50.144
Then Tails is running from USB drive "old" 0.232
And I create a persistent partition 23.590
And I take note of which tps features are available 6.865
Then a Tails persistence partition exists on USB drive "old" 0.707
And I shutdown Tails and wait for the computer to power off 2.746
After features/support/hooks.rb:339 0.489
After features/support/hooks.rb:108 0.006
Tags: @product
1:36.477
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.135
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:3.458
Then Tails is running from USB drive "old" 0.302
And all tps features are active 8.192
When I write some files expected to persist 1.127
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.177
And all persistence configuration files have safe access rights 0.310
And all persistent directories from the old Tails version have safe access rights 1.895
And I take note of which tps features are available 6.712
And I shutdown Tails and wait for the computer to power off 2.613
# 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.553
After features/support/hooks.rb:339 0.451
After features/support/hooks.rb:108 0.012
Tags: @product
2:19.074
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.005
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 9.048
And I log in to a new session 15.042
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.942
And I plug USB drive "to_upgrade" 2.209
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.617
Then the running Tails is installed on USB drive "to_upgrade" 19.967
And I unplug USB drive "to_upgrade" 0.137
And I unplug USB drive "__internal" 0.110
After features/support/hooks.rb:339 2.435
After features/support/hooks.rb:108 0.000
Tags: @product
1:10.931
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Given a computer 0.151
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:4.370
Then all tps features from the old Tails version are active 1.065
And Tails is running from USB drive "to_upgrade" 0.251
And the boot device has safe access rights 2.290
And the expected persistent files created with the old Tails version are present in the filesystem 1.055
And all persistent directories from the old Tails version have safe access rights 1.747
After features/support/hooks.rb:339 0.738
After features/support/hooks.rb:108 0.006
Tags: @product @automatic_upgrade
40:23.645
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.001
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.382
And no SquashFS delta is installed 0.051
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.036
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.186
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.407
When the network is plugged 0.033
And Tor is ready 12.033
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 6:34.963
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 33:27.335
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.362 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:57:10)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/47/artifact/build-artifacts/01:57:10_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/47/artifact/build-artifacts/01:57:10_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/47/artifact/build-artifacts/01:57:10_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21565-flatpak-safe/47/artifact/build-artifacts/01:57:10_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:108 0.000
Tags: @product @automatic_upgrade
2:22.558
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.033
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.214
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.032
And the signing key used by the Upgrader is outdated 0.065
But a current signing key is available on our website 0.000
When the network is plugged 0.030
And Tor is ready 10.371
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 2:3.810
After features/support/hooks.rb:339 0.826
After features/support/hooks.rb:108 0.000