Project Number Date
test_Tails_ISO_feature-trixie 49 09 Jul 2025, 10:42

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:27.355 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
3:44.102
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given a computer 0.272
And I create a 7200 MiB disk named "old" 0.072
And I plug USB drive "old" 1.248
And I write an old version of the Tails USB image to disk "old" 42.797
When I start Tails from USB drive "old" with network unplugged 2:54.239
Then the boot device has safe access rights 4.341
And Tails is running from USB drive "old" 0.387
And there is no persistence partition on USB drive "old" 0.073
And process "udev-watchdog" is running 0.094
And udev-watchdog is monitoring the correct device 0.343
And I unplug USB drive "old" 0.231
After features/support/hooks.rb:330 3.858
After features/support/hooks.rb:100 0.098
Tags: @product
4:31.079
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.010
Given a computer 0.523
And I start Tails from USB drive "old" with network unplugged and I login 3:22.272
Then Tails is running from USB drive "old" 3.812
And I create a persistent partition 45.816
And I take note of which tps features are available 3.098
Then a Tails persistence partition exists on USB drive "old" 0.812
And I shutdown Tails and wait for the computer to power off 14.744
After features/support/hooks.rb:330 0.376
After features/support/hooks.rb:100 0.013
Tags: @product
5:45.122
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Given a computer 0.447
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 4:40.256
Then Tails is running from USB drive "old" 1.067
And all tps features are active 2.203
When I write some files expected to persist 2.160
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.288
And all persistence configuration files have safe access rights 0.495
And all persistent directories from the old Tails version have safe access rights 3.370
And I take note of which tps features are available 1.466
And I shutdown Tails and wait for the computer to power off 11.819
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 41.546
After features/support/hooks.rb:330 0.141
After features/support/hooks.rb:100 0.013
Tags: @product
3:54.474
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 18.697
And I log in to a new session 55.831
And I clone USB drive "old" to a new USB drive "to_upgrade" 2.362
And I plug USB drive "to_upgrade" 2.607
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:53.502
Then the running Tails is installed on USB drive "to_upgrade" 38.012
And I unplug USB drive "to_upgrade" 2.259
And I unplug USB drive "__internal" 1.200
After features/support/hooks.rb:330 4.252
After features/support/hooks.rb:100 0.000
Tags: @product
4:23.202
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.208
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 4:6.339
Then all tps features from the old Tails version are active 6.781
And Tails is running from USB drive "to_upgrade" 0.488
And the boot device has safe access rights 4.753
And the expected persistent files created with the old Tails version are present in the filesystem 1.584
And all persistent directories from the old Tails version have safe access rights 3.046
After features/support/hooks.rb:330 1.813
After features/support/hooks.rb:100 0.032
Tags: @product @automatic_upgrade
23:17.743
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.015
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 19.876
And no SquashFS delta is installed 0.202
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.389
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.079
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.614
And the file system changes introduced in version 6.3~testoverlayfs are not present 3.968
When the network is plugged 1.174
And Tor is ready 28.947
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:22.490
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 9.320 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 04:48:29)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/04:48: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/49/artifact/build-artifacts/04:48:29_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/04:48:29_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/04:48:29_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.000
Tags: @product @automatic_upgrade
23:51.630
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.039
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 37.250
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 2.645
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.186
And the signing key used by the Upgrader is outdated 0.135
But a current signing key is available on our website 0.000
When the network is plugged 0.119
And Tor is ready 52.822
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:18.469
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 13.103 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 05:12:34)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/05:12:34_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/49/artifact/build-artifacts/05:12:34_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/05:12:34_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/49/artifact/build-artifacts/05:12:34_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:100 0.000