Project Number Date
test_Tails_ISO_stable 6385 19 May 2026, 14:01

Failures Overview

The following summary displays scenarios that failed.

Feature: Time syncing
1:47.396
Scenario The system time is not synced to the hardware clock
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Before features/support/hooks.rb:523 0.001
Steps
Given I have started Tails from DVD without network and logged in 6.521
When I bump the system time with "-15 days" 0.339
And I warm reboot the computer 0.005
And the computer reboots Tails 1:40.530
can
can not find any of the patterns ["TailsGreeter.png", "PlymouthGraphicsCardFailureMessage.png"] on the screen (FindFailed)
./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:444:in `/^the computer (?:re)?boots Tails$/'
features/time_syncing.feature:37:in `And the computer reboots Tails'
Then Tails' hardware clock is close to the host system's time 0.000
After features/support/hooks.rb:531 0.045
After features/support/hooks.rb:335 5.379

SCENARIO FAILED: 'The system time is not synced to the hardware clock' (at time 00:10:31)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6385/artifact/build-artifacts/00:10:31_The_system_time_is_not_synced_to_the_hardware_clock.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6385/artifact/build-artifacts/00:10:31_The_system_time_is_not_synced_to_the_hardware_clock.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6385/artifact/build-artifacts/00:10:31_The_system_time_is_not_synced_to_the_hardware_clock.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6385/artifact/build-artifacts/00:10:31_The_system_time_is_not_synced_to_the_hardware_clock.journal

After features/support/hooks.rb:104 0.007
2.247
Scenario All packages are up-to-date
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:548 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 2.246
Command failed (pid 58537 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@f957158a66-20260519T0944Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_stable/tmp/tails-amd64-stable@f957158a66-20260519T0944Z.build-manifest
INFO: Last successful auto-update of the UDD mirror: 2026-05-19 12:05:02+00:00 (0:18:20.341239 ago)
INFO: Need to upgrade to a new APT snapshot:
  - 7zip (25.01+dfsg-1~deb13u1) to Debian trixie (25.01+dfsg-1~deb13u2)
  - base-files (13.8+deb13u4) to Debian trixie (13.8+deb13u5)
  - bash (5.2.37-2+b8) to Debian trixie (5.2.37-2)
  - bubblewrap (0.11.0-2) to Debian trixie (0.11.0-2+deb13u1)
  - busybox (1:1.37.0-6+b7) to Debian trixie (1:1.37.0-6)
  - curl[curl] (8.14.1-2+deb13u2) to Debian trixie (8.14.1-2+deb13u3)
  - curl[libcurl4t64, libcurl3t64-gnutls] (8.14.1-2+deb13u2) to Debian trixie (8.14.1-2+deb13u3)
  - distro-info-data (0.66+deb13u1) to Debian trixie (0.66+deb13u2)
  - e2fsprogs[e2fsprogs] (1.47.2-3+b10) to Debian trixie (1.47.2-3)
  - e2fsprogs[libcom-err2] (1.47.2-3+b10) to Debian trixie (1.47.2-3)
  - e2fsprogs[libext2fs2t64] (1.47.2-3+b10) to Debian trixie (1.47.2-3)
  - e2fsprogs[libss2] (1.47.2-3+b10) to Debian trixie (1.47.2-3)
  - e2fsprogs[logsave] (1.47.2-3+b10) to Debian trixie (1.47.2-3)
  - glib2.0[gir1.2-glib-2.0] (2.84.4-3~deb13u2) to Debian trixie (2.84.4-3~deb13u3)
  - glib2.0[libglib2.0-data, libglib2.0-bin, libglib2.0-0t64] (2.84.4-3~deb13u2) to Debian trixie (2.84.4-3~deb13u3)
  - glibc[libc6-dev, libc-dev-bin, libc6, libc-l10n, libc-bin] (2.41-12+deb13u2) to Debian trixie (2.41-12+deb13u3)
  - glibc[locales] (2.41-12+deb13u2) to Debian trixie (2.41-12+deb13u3)
  - gnupg2[dirmngr] (2.4.7-21+deb13u1+b2) to Debian trixie (2.4.7-21+deb13u1)
  - gnupg2[gpg-agent, gpg, gpgconf, gpgsm] (2.4.7-21+deb13u1+b2) to Debian trixie (2.4.7-21+deb13u1)
  - gnupg2[scdaemon] (2.4.7-21+deb13u1+b2) to Debian trixie (2.4.7-21+deb13u1)
  - grub-efi-amd64-signed (1+2.12+9+deb13u1) to Debian trixie (1+2.12+9+deb13u2)
  - grub2[grub-common, grub-efi-amd64-bin] (2.12-9+deb13u1) to Debian trixie (2.12-9+deb13u2)
  - grub2[grub-efi-ia32-unsigned, grub-efi-ia32, grub-efi-ia32-bin, grub2-common, grub-efi-amd64-unsigned] (2.12-9+deb13u1) to Debian trixie (2.12-9+deb13u2)
  - gvfs (1.57.2-2) to Debian trixie (1.57.2-2+deb13u1)
  - harfbuzz[gir1.2-harfbuzz-0.0] (10.2.0-1+b1) to Debian trixie (10.2.0-1+deb13u1)
  - harfbuzz[libharfbuzz-gobject0, libharfbuzz0b, libharfbuzz-icu0, libharfbuzz-subset0] (10.2.0-1+b1) to Debian trixie (10.2.0-1+deb13u1)
  - initramfs-tools (0.148.3) to Debian trixie (0.148.4)
  - jpeg-xl (0.11.1-4) to Debian trixie (0.11.2-0.1~deb13u1)
  - jq[jq] (1.7.1-6+deb13u1) to Debian trixie (1.7.1-6+deb13u2)
  - jq[libjq1] (1.7.1-6+deb13u1) to Debian trixie (1.7.1-6+deb13u2)
  - libarchive (3.7.4-4) to Debian trixie (3.7.4-4+deb13u1)
  - libcap2 (1:2.75-10+b8) to Debian trixie (1:2.75-10+deb13u1)
  - libcdio (2.2.0-4) to Debian trixie (2.2.0-4.1~deb13u1)
  - libdatetime-timezone-perl (1:2.65-1+2025b) to Debian trixie (1:2.65-1+2026b)
  - libexif (0.6.25-1) to Debian trixie (0.6.25-1+deb13u1)
  - nano (8.4-1) to Debian trixie (8.4-1+deb13u1)
  - orca (48.1-1+deb13u1) to Debian trixie (48.1-1+deb13u2)
  - python3.13[libpython3.13-stdlib, libpython3.13-minimal, libpython3.13] (3.13.5-2) to Debian trixie (3.13.5-2+deb13u2)
  - python3.13[python3.13, python3.13-minimal] (3.13.5-2) to Debian trixie (3.13.5-2+deb13u2)
  - qt6-base (6.8.2+dfsg-9+deb13u1) to Debian trixie (6.8.2+dfsg-9+deb13u2)
  - rsync (3.4.1+ds1-5+deb13u1) to Debian trixie (3.4.1+ds1-5+deb13u2)
  - sed (4.9-2) to Debian trixie (4.9-2+deb13u1)
  - sudo (1.9.16p2-3+deb13u1) to Debian trixie (1.9.16p2-3+deb13u2)
  - systemd[libnss-systemd, libpam-systemd] (257.9-1~deb13u1) to Debian trixie (257.13-1~deb13u1)
  - systemd[libudev1, libudev-dev, libsystemd0, libsystemd-shared] (257.9-1~deb13u1) to Debian trixie (257.13-1~deb13u1)
  - systemd[systemd, systemd-timesyncd, systemd-sysv, systemd-oomd] (257.9-1~deb13u1) to Debian trixie (257.13-1~deb13u1)
  - systemd[udev] (257.9-1~deb13u1) to Debian trixie (257.13-1~deb13u1)
  - tzdata (2026a-0+deb13u1) to Debian trixie (2026b-0+deb13u1)
 (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:555 0.000
After features/support/hooks.rb:104 0.000
Tags: @product
1:22.961
Scenario The Tor Browser cannot access the LAN
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.008
Steps
Given I have started Tails from DVD and logged in and the network is connected 10.340
And a web server is running on the LAN 1.038
And I capture all network traffic 0.004
When I start the Tor Browser 7.492
And I open a page on the LAN web server in the Tor Browser 4.085
Then the Tor Browser shows the "Unable to connect" error 1:0.000
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/browser.rb:383:in `/^the (Tor|Unsafe) Browser shows the "([^"]+)" error$/'
features/torified_browsing.feature:13:in `Then the Tor Browser shows the "Unable to connect" error'
And no traffic was sent to the web server on the LAN 0.000
After features/support/hooks.rb:335 5.600

SCENARIO FAILED: 'The Tor Browser cannot access the LAN' (at time 03:24:26)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6385/artifact/build-artifacts/03:24:26_The_Tor_Browser_cannot_access_the_LAN.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6385/artifact/build-artifacts/03:24:26_The_Tor_Browser_cannot_access_the_LAN.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6385/artifact/build-artifacts/03:24:26_The_Tor_Browser_cannot_access_the_LAN.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6385/artifact/build-artifacts/03:24:26_The_Tor_Browser_cannot_access_the_LAN.journal

After features/support/hooks.rb:104 0.044