Project Number Date
test_Tails_ISO_feature-trixie 38 25 Jun 2025, 08:14

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:2:37.761 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:23.467
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.199
And I create a 7200 MiB disk named "old" 0.057
And I plug USB drive "old" 1.054
And I write an old version of the Tails USB image to disk "old" 28.803
When I start Tails from USB drive "old" with network unplugged 2:48.654
Then the boot device has safe access rights 3.577
And Tails is running from USB drive "old" 0.374
And there is no persistence partition on USB drive "old" 0.072
And process "udev-watchdog" is running 0.091
And udev-watchdog is monitoring the correct device 0.345
And I unplug USB drive "old" 0.236
After features/support/hooks.rb:330 3.853
After features/support/hooks.rb:100 0.009
Tags: @product
3:23.852
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given a computer 0.227
And I start Tails from USB drive "old" with network unplugged and I login 2:35.998
Then Tails is running from USB drive "old" 0.835
And I create a persistent partition 31.824
And I take note of which tps features are available 3.170
Then a Tails persistence partition exists on USB drive "old" 0.867
And I shutdown Tails and wait for the computer to power off 10.929
After features/support/hooks.rb:330 0.195
After features/support/hooks.rb:100 0.009
Tags: @product
4:4.844
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:18.987
Then Tails is running from USB drive "old" 1.015
And all tps features are active 2.934
When I write some files expected to persist 2.497
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.213
And all persistence configuration files have safe access rights 0.543
And all persistent directories from the old Tails version have safe access rights 2.726
And I take note of which tps features are available 0.500
And I shutdown Tails and wait for the computer to power off 7.537
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 27.692
After features/support/hooks.rb:330 0.254
After features/support/hooks.rb:100 0.010
Tags: @product
2:51.031
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 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 10.410
And I log in to a new session 34.439
And I clone USB drive "old" to a new USB drive "to_upgrade" 1.724
And I plug USB drive "to_upgrade" 2.635
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:36.759
Then the running Tails is installed on USB drive "to_upgrade" 24.630
And I unplug USB drive "to_upgrade" 0.230
And I unplug USB drive "__internal" 0.200
After features/support/hooks.rb:330 3.567
After features/support/hooks.rb:100 0.000
Tags: @product
3:15.206
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Given a computer 0.187
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:3.036
Then all tps features from the old Tails version are active 3.126
And Tails is running from USB drive "to_upgrade" 0.480
And the boot device has safe access rights 4.086
And the expected persistent files created with the old Tails version are present in the filesystem 1.715
And all persistent directories from the old Tails version have safe access rights 2.573
After features/support/hooks.rb:330 0.687
After features/support/hooks.rb:100 0.007
Tags: @product @automatic_upgrade
22:53.061
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.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 13.762
And no SquashFS delta is installed 0.440
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.528
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.048
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.363
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.486
When the network is plugged 0.103
And Tor is ready 23.891
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:13.435
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 5.678 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 03:10:42)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/03:10:42_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/38/artifact/build-artifacts/03:10:42_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/03:10:42_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/03:10:42_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:100 0.000
Tags: @product @automatic_upgrade
22:46.299
Scenario Upgrading a Tails whose signing key is outdated
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.982
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.582
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.285
And the signing key used by the Upgrader is outdated 0.161
But a current signing key is available on our website 0.000
When the network is plugged 0.095
And Tor is ready 21.143
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 22:13.048
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 5.596 
SCENARIO FAILED: 'Upgrading a Tails whose signing key is outdated' (at time 03:33:34)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/03:33: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/38/artifact/build-artifacts/03:33:34_Upgrading_a_Tails_whose_signing_key_is_outdated.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/03:33:34_Upgrading_a_Tails_whose_signing_key_is_outdated.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/38/artifact/build-artifacts/03:33:34_Upgrading_a_Tails_whose_signing_key_is_outdated.journal
After features/support/hooks.rb:100 0.000