Project Number Date
test_Tails_ISO_stable 5983 04 Dec 2025, 19:40

Failures Overview

The following summary displays scenarios that failed.

Feature: Packages are up-to-date
Tags: @source
4.648
Scenario All packages are up-to-date
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:544 0.000
Steps
Given I have the build manifest for the image under test 0.000
Then all packages listed in the build manifest are up-to-date 4.648
Command 
Command failed (pid 45302 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_stable/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_stable/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_stable/tmp/tails-amd64-stable@b065a39dfb-20251204T1435Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_stable/tmp/tails-amd64-stable@b065a39dfb-20251204T1435Z.build-manifest
INFO: Last successful auto-update of the UDD mirror: 2025-12-04 18:05:02+00:00 (0:05:16.011055 ago)
WARNING: tor-geoipdb: the package version (0.4.8.21-1~d13.trixie+1) is higher than the newest version in Debian (0.4.8.16-1)
WARNING: tor: the package version (0.4.8.21-1~d13.trixie+1) is higher than the newest version in Debian (0.4.8.16-1)
INFO: Need to upgrade to a new APT snapshot:
  - firmware-nonfree (20251021-1) to Debian forky (20251111-1)
 (CommandFailed)
/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/support/helpers/misc_helpers.rb:332:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/support/helpers/misc_helpers.rb:319:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/support/helpers/misc_helpers.rb:319:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/step_definitions/needed_package_updates.rb:8:in `/^all packages listed in the build manifest are up-to-date$/'
features/needed_package_updates.feature:12:in `Then all packages listed in the build manifest are up-to-date'
After features/support/hooks.rb:551 0.000
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
2:10.967
Scenario LUKS backup header is restored if something goes wrong during 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 LUKS 1 persistent partition and stopped at Tails Greeter's login screen 9.660
And I enable persistence but something goes wrong during the LUKS header upgrade 2:1.306
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/usb.rb:686:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:704:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:714:in `/^I enable persistence but something goes wrong during the LUKS header upgrade$/'
features/persistence.feature:162:in `And I enable persistence but something goes wrong during the LUKS header upgrade'
Then the Tails persistence partition on USB drive "__internal" still has LUKS version 1 0.000
After features/support/hooks.rb:331 5.334 
SCENARIO FAILED: 'LUKS backup header is restored if something goes wrong during upgrade' (at time 03:06:27)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5983/artifact/build-artifacts/03:06:27_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5983/artifact/build-artifacts/03:06:27_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5983/artifact/build-artifacts/03:06:27_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5983/artifact/build-artifacts/03:06:27_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.journal
After features/support/hooks.rb:100 0.000