Project Number Date
test_Tails_ISO_stable 5966 24 Nov 2025, 12:43

Failures Overview

The following summary displays scenarios that failed.

Feature: Upgrading an old Tails USB installation
Tags: @product
3:1.692
Scenario Creating a persistent partition with the old Tails USB installation
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given a computer 0.179
And I start Tails from USB drive "old" with network unplugged and I login 3:1.512
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:396: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:393:in `enter_boot_menu_cmdline'
./features/step_definitions/common_steps.rb:443:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:280: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:393:in `enter_boot_menu_cmdline'
./features/step_definitions/common_steps.rb:443:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:280: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_upgrade.feature:36:in `And I start Tails from USB drive "old" with network unplugged and I login'
Then Tails is running from USB drive "old" 0.000
And I create a persistent partition 0.000
And I take note of which tps features are available 0.000
Then a Tails persistence partition exists on USB drive "old" 0.000
And I shutdown Tails and wait for the computer to power off 0.000
After features/support/hooks.rb:331 10.738 
SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 01:30:54)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5966/artifact/build-artifacts/01:30:54_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5966/artifact/build-artifacts/01:30:54_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5966/artifact/build-artifacts/01:30:54_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.096
Feature: Upgrading an old Tails USB installation
Tags: @product
3:1.569
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given a computer 0.180
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 3:1.388
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:396: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:393:in `enter_boot_menu_cmdline'
./features/step_definitions/common_steps.rb:443:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:280: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:393:in `enter_boot_menu_cmdline'
./features/step_definitions/common_steps.rb:443:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:280: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_upgrade.feature:46:in `And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled'
Then Tails is running from USB drive "old" 0.000
And all tps features are active 0.000
When I write some files expected to persist 0.000
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.000
And all persistence configuration files have safe access rights 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
And I take note of which tps features are available 0.000
And I shutdown Tails and wait for the computer to power off 0.000
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 0.000
After features/support/hooks.rb:331 10.858 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 01:34:07)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5966/artifact/build-artifacts/01:34:07_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5966/artifact/build-artifacts/01:34:07_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5966/artifact/build-artifacts/01:34:07_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.111
Feature: Upgrading an old Tails USB installation
Tags: @product
3:1.568
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given a computer 0.156
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 3:1.411
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:396: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:393:in `enter_boot_menu_cmdline'
./features/step_definitions/common_steps.rb:443:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:280: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:393:in `enter_boot_menu_cmdline'
./features/step_definitions/common_steps.rb:443:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:280: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_upgrade.feature:73:in `And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled'
Then all tps features from the old Tails version are active 0.000
And Tails is running from USB drive "to_upgrade" 0.000
And the boot device has safe access rights 0.000
And the expected persistent files created with the old Tails version are present in the filesystem 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
After features/support/hooks.rb:331 10.927 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:40:21)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5966/artifact/build-artifacts/01:40:21_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5966/artifact/build-artifacts/01:40:21_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5966/artifact/build-artifacts/01:40:21_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.138
Feature: Packages are up-to-date
Tags: @source
4.040
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.040
Command 
Command failed (pid 55408 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@412d9e1ce9-20251124T0724Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_stable/tmp/tails-amd64-stable@412d9e1ce9-20251124T0724Z.build-manifest
INFO: Last successful auto-update of the UDD mirror: 2025-11-24 10:05:02+00:00 (0:58:33.478206 ago)
WARNING: tor-geoipdb: the package version (0.4.8.19-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.19-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:
  - 7zip (24.09+dfsg-8) to Debian trixie (25.01+dfsg-1~deb13u1)
  - base-files (13.8+deb13u1) to Debian trixie (13.8+deb13u2)
  - brltty[libbrlapi0.8] (6.7-3.1) to Debian trixie (6.7-3.1+deb13u2)
  - brltty[python3-brlapi] (6.7-3.1) to Debian trixie (6.7-3.1+deb13u2)
  - console-setup[console-setup-linux, console-setup] (1.240) to Debian trixie (1.242~deb13u1)
  - console-setup[keyboard-configuration] (1.240) to Debian trixie (1.242~deb13u1)
  - curl[curl] (8.14.1-2) to Debian trixie (8.14.1-2+deb13u2)
  - curl[libcurl3t64-gnutls, libcurl4t64] (8.14.1-2) to Debian trixie (8.14.1-2+deb13u2)
  - dhcpcd (1:10.1.0-11) to Debian trixie (1:10.1.0-11+deb13u1)
  - distro-info-data (0.66) to Debian trixie (0.66+deb13u1)
  - dkms (3.2.0-1) to Debian trixie (3.2.2-1~deb13u1)
  - evolution-data-server[evolution-data-server-common] (3.56.1-2) to Debian trixie (3.56.2-0+deb13u1)
  - evolution-data-server[libcamel-1.2-64t64] (3.56.1-2) to Debian trixie (3.56.2-0+deb13u1)
  - evolution-data-server[libecal-2.0-3, libedataserver-1.2-27t64] (3.56.1-2) to Debian trixie (3.56.2-0+deb13u1)
  - fluidsynth (2.4.4+dfsg-1) to Debian trixie (2.4.4+dfsg-1+deb13u1)
  - gnome-session (48.0-1) to Debian trixie (48.0-1+deb13u1)
  - libssh (0.11.2-1) to Debian trixie (0.11.2-1+deb13u1)
  - malcontent (0.13.0-2) to Debian trixie (0.13.0-2+deb13u1)
  - open-vm-tools (2:12.5.0-2) to Debian trixie (2:12.5.0-2+deb13u1)
  - poppler[gir1.2-poppler-0.18] (25.03.0-5) to Debian trixie (25.03.0-5+deb13u2)
  - poppler[libpoppler-glib8t64, libpoppler-cpp2, libpoppler147] (25.03.0-5) to Debian trixie (25.03.0-5+deb13u2)
  - poppler[poppler-utils] (25.03.0-5) to Debian trixie (25.03.0-5+deb13u2)
  - python-eventlet (0.39.1-2) to Debian trixie (0.39.1-2+deb13u1)
  - qt6-base (6.8.2+dfsg-9) to Debian trixie (6.8.2+dfsg-9+deb13u1)
  - samba[libldb2] (2:2.11.0+samba4.22.4+dfsg-1~deb13u1) to Debian trixie (2:4.22.6+dfsg-0+deb13u1)
  - samba[libsmbclient0] (2:4.22.4+dfsg-1~deb13u1) to Debian trixie (2:4.22.6+dfsg-0+deb13u1)
  - samba[libtevent0t64, libtdb1, libtalloc2] (2:2.4.3+samba4.22.4+dfsg-1~deb13u1) to Debian trixie (2:4.22.6+dfsg-0+deb13u1)
  - samba[libwbclient0] (2:4.22.4+dfsg-1~deb13u1) to Debian trixie (2:4.22.6+dfsg-0+deb13u1)
  - samba[samba-libs] (2:4.22.4+dfsg-1~deb13u1) to Debian trixie (2:4.22.6+dfsg-0+deb13u1)
  - systemd[libnss-systemd, libpam-systemd] (257.8-1~deb13u2) to Debian trixie (257.9-1~deb13u1)
  - systemd[libsystemd-shared, libsystemd0] (257.8-1~deb13u2) to Debian trixie (257.9-1~deb13u1)
  - systemd[libudev-dev, libudev1] (257.8-1~deb13u2) to Debian trixie (257.9-1~deb13u1)
  - systemd[systemd, systemd-sysv, udev, systemd-oomd, systemd-timesyncd] (257.8-1~deb13u2) to Debian trixie (257.9-1~deb13u1)
  - xorg (1:7.7+24) to Debian trixie (1:7.7+24+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: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