Project Number Date
test_Tails_ISO_stable 6323 22 Apr 2026, 12:00

Failures Overview

The following summary displays scenarios that failed.

Tags: @product
3:1.261
Scenario The system partition is updated when booting from a USB drive where a Tails USB image was copied
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given a computer 0.055
And I start Tails from USB drive "usbimage" with network unplugged and I login 3:1.205
try_for() timeout expired
Last ignored exception was: FindFailed: can not find any of the patterns ["TailsBootMenuSyslinux.png", "TailsBootMenuSyslinux_alt.png"] on the screen
./features/support/helpers/screen.rb:248:in `rescue in wait_any'
./features/support/helpers/screen.rb:232:in `wait_any'
./features/step_definitions/common_steps.rb:354:in `block in enter_boot_menu_cmdline'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
<internal:kernel>:187:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/common_steps.rb:351:in `enter_boot_menu_cmdline'
./features/step_definitions/common_steps.rb:403:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:235:in `block in <top (required)>' (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/common_steps.rb:351:in `enter_boot_menu_cmdline'
./features/step_definitions/common_steps.rb:403:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:235:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/usb_install.feature:100:in `And I start Tails from USB drive "usbimage" with network unplugged and I login'
Then Tails is running from USB drive "usbimage" 0.000
And the label of the system partition on "usbimage" is "Tails" 0.000
And the system partition on "usbimage" is an EFI system partition 0.000
And the FAT filesystem on the system partition on "usbimage" is at least 4000M large 0.000
And the UUID of the FAT filesystem on the system partition on "usbimage" was randomized 0.000
And the label of the FAT filesystem on the system partition on "usbimage" is "TAILS" 0.000
And the system partition on "usbimage" has the expected flags 0.000
After features/support/hooks.rb:331 10.607

SCENARIO FAILED: 'The system partition is updated when booting from a USB drive where a Tails USB image was copied' (at time 00:50:07)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6323/artifact/build-artifacts/00:50:07_The_system_partition_is_updated_when_booting_from_a_USB_drive_where_a_Tails_USB_image_was_copied.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6323/artifact/build-artifacts/00:50:07_The_system_partition_is_updated_when_booting_from_a_USB_drive_where_a_Tails_USB_image_was_copied.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6323/artifact/build-artifacts/00:50:07_The_system_partition_is_updated_when_booting_from_a_USB_drive_where_a_Tails_USB_image_was_copied.journal

After features/support/hooks.rb:100 0.063
0.547
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 0.547
Command failed (pid 63837 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-7.7.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_stable/tmp/tails-amd64-7.7.build-manifest
INFO: Last successful auto-update of the UDD mirror: 2026-04-22 10:05:02+00:00 (0:10:47.962196 ago)
INFO: Need to upgrade to a new APT snapshot:
  - electrum (4.7.0+dfsg-1~bpo13+1) to Debian trixie-backports (4.7.2+dfsg-1~bpo13+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:10:in `/^all packages listed in the build manifest are up-to-date$/'
features/needed_package_updates.feature:13: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
Tags: @product
1:31.330
Scenario Tails Persistent Storage behave tests
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails from DVD and logged in with an administration password and the network is connected 1:31.330
Known issue #21211: timed out while waiting for the GNOME Shell Introspect API (RuntimeError)
./features/step_definitions/common_steps.rb:399:in `rescue in wait_for_ponytail'
./features/step_definitions/common_steps.rb:388:in `wait_for_ponytail'
./features/step_definitions/common_steps.rb:626:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:542:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:137:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ with\ an\ administration\ password\ and\ the\ network\ is\ connected$/'
features/persistence.feature:7:in `Given I have started Tails from DVD and logged in with an administration password and the network is connected'
And I update APT using apt 0.000
And I install "python3-behave" using apt 0.000
Then the Tails Persistent Storage behave tests pass 0.000
After features/support/hooks.rb:331 11.293

SCENARIO FAILED: 'Tails Persistent Storage behave tests' (at time 02:25:59)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6323/artifact/build-artifacts/02:25:59_Tails_Persistent_Storage_behave_tests.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6323/artifact/build-artifacts/02:25:59_Tails_Persistent_Storage_behave_tests.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6323/artifact/build-artifacts/02:25:59_Tails_Persistent_Storage_behave_tests.journal

After features/support/hooks.rb:100 0.000