Project Number Date
test_Tails_ISO_devel 3822 19 May 2025, 18:00

Failures Overview

The following summary displays scenarios that failed.

Feature: Installing Tails to a USB drive
Tags: @product
3:1.751
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.179
And I start Tails from USB drive "usbimage" with network unplugged and I login 3:1.571
try_for() 
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:407:in `block in enter_boot_menu_cmdline'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66: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:404:in `enter_boot_menu_cmdline'
./features/step_definitions/common_steps.rb:442:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:284: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:404:in `enter_boot_menu_cmdline'
./features/step_definitions/common_steps.rb:442:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:284: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:330 10.556 
SCENARIO FAILED: 'The system partition is updated when booting from a USB drive where a Tails USB image was copied' (at time 01:05:53)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3822/artifact/build-artifacts/01:05:53_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_devel/3822/artifact/build-artifacts/01:05:53_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_devel/3822/artifact/build-artifacts/01:05:53_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.064
Feature: Packages are up-to-date
Tags: @source
5.711
Scenario All packages are up-to-date
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:538 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 5.711
Command 
Command failed (returned pid 58758 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_devel/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_devel/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_devel/tmp/tails-amd64-devel@b43140903f-20250519T1042Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_devel/tmp/tails-amd64-devel@b43140903f-20250519T1042Z.build-manifest
INFO: Need to upgrade our own forked package:
  - network-manager (1.42.4-1.0tails1) to Debian bookworm (1.42.4-1+deb12u1)
INFO: Need to upgrade to a new APT snapshot:
  - flatpak (1.14.10-1~deb12u1+tails1) to Debian bookworm-backports (1.16.0-2~bpo12+1)
.
<0> expected but was
<#<Process::Status: pid 58758 exit 1>>. (Test::Unit::AssertionFailedError)
/var/lib/jenkins/workspace/test_Tails_ISO_devel/features/support/helpers/misc_helpers.rb:307:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_devel/features/support/helpers/misc_helpers.rb:303:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_devel/features/support/helpers/misc_helpers.rb:303:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_devel/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:545 0.000
After features/support/hooks.rb:100 0.000