Cucumber Reports (no 5657) - Failures Overview

Project	Number	Date
test_Tails_ISO_stable	5657	19 May 2025, 13:28

Feature: Installing Tails to a USB drive

Tags: @product

15:35.399

Scenario Installing Tails with Tails Installer to a used USB drive, cloning the Persistent Storage

Hooks

Before features/support/hooks.rb:266 0.000

Before features/support/hooks.rb:273 0.003

Steps

Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.958

And I create a file in the Persistent directory 0.082

And I temporarily create a 7200 MiB disk named "install" 0.039

And I create a gpt partition with a vfat filesystem on disk "install" 6.420

And I plug USB drive "install" 2.510

And I install Tails with Persistent Storage to USB drive "install" by cloning 15:14.388

try_for()

try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | tails-installer]: child with name="Information" roleName='alert'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/usb.rb:263:in `block (2 levels) in <top (required)>'
./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/usb.rb:261: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/usb.rb:261:in `/^I (install|reinstall|upgrade) Tails( with Persistent Storage)? (?:to|on) USB drive "([^"]+)" by cloning$/'
features/usb_install.feature:50:in `And I install Tails with Persistent Storage to USB drive "install" by cloning'

Then the running Tails is installed on USB drive "install" 0.000

And there is a random seed on USB drive "install" 0.000

And there is a persistence partition on USB drive "install" 0.000

And the USB drive "install" contains the same files as my persistent storage 0.000

Hooks

After features/support/hooks.rb:330 9.104

Output 1

SCENARIO FAILED: 'Installing Tails with Tails Installer to a used USB drive, cloning the Persistent Storage' (at time 01:01:35)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5657/artifact/build-artifacts/01:01:35_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5657/artifact/build-artifacts/01:01:35_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5657/artifact/build-artifacts/01:01:35_Installing_Tails_with_Tails_Installer_to_a_used_USB_drive,_cloning_the_Persistent_Storage.journal

After features/support/hooks.rb:100 0.129

Feature: Packages are up-to-date

Tags: @source

3.499

Scenario All packages are up-to-date

Hooks

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 3.499

Command

Command failed (returned pid 57040 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@c30ee85c5a-20250519T0716Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_stable/tmp/tails-amd64-stable@c30ee85c5a-20250519T0716Z.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:
  - abseil (20220623.1-1) to Debian bookworm (20220623.1-1+deb12u2)
  - base-files (12.4+deb12u10) to Debian bookworm (12.4+deb12u11)
  - bash (5.2.15-2+b7) to Debian bookworm (5.2.15-2)
  - busybox (1:1.35.0-4+b3) to Debian bookworm (1:1.35.0-4)
  - debian-archive-keyring (2023.3+deb12u1) to Debian bookworm (2023.3+deb12u2)
  - distro-info-data (0.58+deb12u3) to Debian bookworm (0.58+deb12u4)
  - flatpak[flatpak] (1.14.10-1~deb12u1+tails1) to Debian bookworm-backports (1.16.0-2~bpo12+1)
  - flatpak[gir1.2-flatpak-1.0] (1.14.10-1~deb12u1+tails1) to Debian bookworm-backports (1.16.0-2~bpo12+1)
  - flatpak[libflatpak0] (1.14.10-1~deb12u1+tails1) to Debian bookworm-backports (1.16.0-2~bpo12+1)
  - gcc-12[cpp-12] (12.2.0-14) to Debian bookworm (12.2.0-14+deb12u1)
  - gcc-12[gcc-12, g++-12, gcc-12-base] (12.2.0-14) to Debian bookworm (12.2.0-14+deb12u1)
  - gcc-12[libatomic1, libasan8] (12.2.0-14) to Debian bookworm (12.2.0-14+deb12u1)
  - gcc-12[libcc1-0] (12.2.0-14) to Debian bookworm (12.2.0-14+deb12u1)
  - gcc-12[libgfortran5, libgcc-12-dev, libgcc-s1] (12.2.0-14) to Debian bookworm (12.2.0-14+deb12u1)
  - gcc-12[libitm1, liblsan0, libgomp1] (12.2.0-14) to Debian bookworm (12.2.0-14+deb12u1)
  - gcc-12[libobjc4] (12.2.0-14) to Debian bookworm (12.2.0-14+deb12u1)
  - gcc-12[libquadmath0] (12.2.0-14) to Debian bookworm (12.2.0-14+deb12u1)
  - gcc-12[libstdc++6, libtsan2, libubsan1, libstdc++-12-dev] (12.2.0-14) to Debian bookworm (12.2.0-14+deb12u1)
  - glib2.0 (2.74.6-2+deb12u5) to Debian bookworm (2.74.6-2+deb12u6)
  - imagemagick[imagemagick-6-common] (8:6.9.11.60+dfsg-1.6+deb12u2) to Debian bookworm (8:6.9.11.60+dfsg-1.6+deb12u3)
  - imagemagick[libmagick++-6.q16-8, libmagickwand-6.q16-6, libmagickcore-6.q16-6] (8:6.9.11.60+dfsg-1.6+deb12u2) to Debian bookworm (8:6.9.11.60+dfsg-1.6+deb12u3)
  - initramfs-tools (0.142+deb12u1) to Debian bookworm (0.142+deb12u3)
  - libcap2 (1:2.66-4) to Debian bookworm (1:2.66-4+deb12u1)
  - openssl[libssl3] (3.0.15-1~deb12u1) to Debian bookworm (3.0.16-1~deb12u1)
  - openssl[openssl] (3.0.15-1~deb12u1) to Debian bookworm (3.0.16-1~deb12u1)
  - poppler[gir1.2-poppler-0.18] (22.12.0-2+b1) to Debian bookworm (22.12.0-2+deb12u1)
  - poppler[libpoppler-glib8, libpoppler126, libpoppler-cpp0v5] (22.12.0-2+b1) to Debian bookworm (22.12.0-2+deb12u1)
  - poppler[poppler-utils] (22.12.0-2+b1) to Debian bookworm (22.12.0-2+deb12u1)
  - python3.11[libpython3.11-stdlib, libpython3.11, libpython3.11-minimal] (3.11.2-6+deb12u5) to Debian bookworm (3.11.2-6+deb12u6)
  - python3.11[python3.11, python3.11-minimal] (3.11.2-6+deb12u5) to Debian bookworm (3.11.2-6+deb12u6)
  - qtbase-opensource-src (5.15.8+dfsg-11+deb12u2) to Debian bookworm (5.15.8+dfsg-11+deb12u3)
  - shadow[login] (1:4.13+dfsg1-1+b1) to Debian bookworm (1:4.13+dfsg1-1+deb12u1)
  - shadow[passwd] (1:4.13+dfsg1-1+b1) to Debian bookworm (1:4.13+dfsg1-1+deb12u1)
  - tzdata (2025a-0+deb12u1) to Debian bookworm (2025b-0+deb12u1)
  - wireless-regdb (2022.06.06-1) to Debian bookworm (2025.02.20-1~deb12u1)
.
<0> expected but was
<#<Process::Status: pid 57040 exit 1>>. (Test::Unit::AssertionFailedError)
/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/support/helpers/misc_helpers.rb:307:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/support/helpers/misc_helpers.rb:303:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/support/helpers/misc_helpers.rb:303: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'

Hooks

After features/support/hooks.rb:545 0.000

After features/support/hooks.rb:100 0.000