Project Number Date
test_Tails_ISO_feature-trixie 32 18 Jun 2025, 09:51

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Upgrading an old Tails USB installation 59 2 26 0 0 87 5 2 7 1:9:7.059 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
4:59.535
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given a computer 0.219
And I create a 7200 MiB disk named "old" 0.049
And I plug USB drive "old" 1.063
And I write an old version of the Tails USB image to disk "old" 1:3.527
When I start Tails from USB drive "old" with network unplugged 3:44.412
Then the boot device has safe access rights 9.197
And Tails is running from USB drive "old" 0.388
And there is no persistence partition on USB drive "old" 0.076
And process "udev-watchdog" is running 0.110
And udev-watchdog is monitoring the correct device 0.302
And I unplug USB drive "old" 0.187
After features/support/hooks.rb:330 3.871
After features/support/hooks.rb:100 0.008
Tags: @product
4:36.448
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given a computer 0.214
And I start Tails from USB drive "old" with network unplugged and I login 3:28.370
Then Tails is running from USB drive "old" 2.518
And I create a persistent partition 46.111
And I take note of which tps features are available 3.236
Then a Tails persistence partition exists on USB drive "old" 1.063
And I shutdown Tails and wait for the computer to power off 14.933
After features/support/hooks.rb:330 0.169
After features/support/hooks.rb:100 0.010
Tags: @product
5:30.795
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.228
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 4:26.678
Then Tails is running from USB drive "old" 4.239
And all tps features are active 3.554
When I write some files expected to persist 2.441
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.231
And all persistence configuration files have safe access rights 0.425
And all persistent directories from the old Tails version have safe access rights 2.706
And I take note of which tps features are available 0.714
And I shutdown Tails and wait for the computer to power off 13.349
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 36.225
After features/support/hooks.rb:330 0.414
After features/support/hooks.rb:100 0.042
Tags: @product
3:43.060
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.025
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.988
And I log in to a new session 56.418
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.185
And I plug USB drive "to_upgrade" 2.972
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:55.296
Then the running Tails is installed on USB drive "to_upgrade" 33.597
And I unplug USB drive "to_upgrade" 0.266
And I unplug USB drive "__internal" 0.334
After features/support/hooks.rb:330 3.935
After features/support/hooks.rb:100 0.000
Tags: @product
3:58.345
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.211
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:41.094
Then all tps features from the old Tails version are active 2.787
And Tails is running from USB drive "to_upgrade" 0.546
And the boot device has safe access rights 6.380
And the expected persistent files created with the old Tails version are present in the filesystem 3.989
And all persistent directories from the old Tails version have safe access rights 3.337
After features/support/hooks.rb:330 1.304
After features/support/hooks.rb:100 0.009
Tags: @product @automatic_upgrade
23:13.721
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.698
And no SquashFS delta is installed 0.113
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.426
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.072
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.362
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.478
When the network is plugged 0.068
And Tor is ready 28.495
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:24.005
Tor 
Tor operation failed (despite retrying 10 times) with
FindFailed: can not find any of the patterns ["TailsUpgraderUpgradeTo6.2~testoverlayfs.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'
./features/support/helpers/misc_helpers.rb:208: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:1301:in `/^I am proposed to install an incremental upgrade to version (.+)$/'
features/usb_upgrade.feature:90:in `Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs'
And I can successfully install the incremental upgrade to version 6.2~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.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:330 6.436 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 03:55:29)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/03:55:29_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/03:55:29_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/03:55:29_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/03:55:29_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.000
Tags: @product @automatic_upgrade
23:5.151
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 15.003
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 1.314
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.114
And the signing key used by the Upgrader is outdated 0.150
But a current signing key is available on our website 0.000
When the network is plugged 0.109
And Tor is ready 23.678
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:24.780
Tor 
Tor operation failed (despite retrying 10 times) with
FindFailed: can not find any of the patterns ["TailsUpgraderUpgradeTo6.2~testoverlayfs.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'
./features/support/helpers/misc_helpers.rb:208: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:1301:in `/^I am proposed to install an incremental upgrade to version (.+)$/'
features/usb_upgrade.feature:134:in `Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs'
After features/support/hooks.rb:330 8.519 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 04:18:42)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/04:18:42_Upgrading_a_Tails_whose_signing_key_is_outdated.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/04:18:42_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/04:18:42_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/32/artifact/build-artifacts/04:18:42_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:100 0.000