Project Number Date
test_Tails_ISO_stable 6250 31 Mar 2026, 11:34

Failures Overview

The following summary displays scenarios that failed.

Feature: Backing up the persistent storage
Tags: @product
2:0.865
Scenario Using Tails' custom backup tool to backup a newly added file
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 20.841
# The volume cannot be in use when GuestFs clones it, which we do below
And I shutdown Tails and wait for the computer to power off 9.676
And I clone USB drive "__internal" to a temporary USB drive "backup" 1.157
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.029
And I write a file "/live/persistence/TailsData_unlocked/new" with contents "foo" 0.010
When I start Tails' custom backup tool 6.935
Then the backup tool displays "Plug in your backup Tails USB stick" 0.207
When I plug USB drive "backup" 2.380
And I give the Persistent Storage on drive "backup" its own UUID 0.189
And I click "Retry" in the backup tool 3.344
Then the backup tool displays "Do you want to back up your Persistent Storage now?" 0.157
When I click "Back Up" in the backup tool 3.108
And I enter my persistent storage passphrase into the polkit prompt 3.824
Then the backup tool displays "Your Persistent Storage was backed up successfully to your backup Tails USB stick!" 1:0.000
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'zenity' application
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/backup.rb:7:in `new'
./features/step_definitions/backup.rb:7:in `block (2 levels) in <top (required)>'
./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/backup.rb:6: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/backup.rb:6:in `/^the backup tool displays "([^"]+)"$/'
features/backup.feature:22:in `Then the backup tool displays "Your Persistent Storage was backed up successfully to your backup Tails USB stick!"'
# The backup tool ejects the drive, so we have to replug it
When I unplug USB drive "backup" 0.000
And I plug USB drive "backup" 0.000
Then the USB drive "backup" contains the same files as my persistent storage 0.000
After features/support/hooks.rb:331 5.881 
SCENARIO FAILED: 'Using Tails' custom backup tool to backup a newly added file' (at time 01:21:52)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6250/artifact/build-artifacts/01:21:52_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6250/artifact/build-artifacts/01:21:52_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6250/artifact/build-artifacts/01:21:52_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6250/artifact/build-artifacts/01:21:52_Using_Tails__custom_backup_tool_to_backup_a_newly_added_file.journal
After features/support/hooks.rb:100 0.115
Feature: Packages are up-to-date
Tags: @source
3.606
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 3.606
Command 
Command failed (pid 97205 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@39e5466df9-20260331T0716Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_stable/tmp/tails-amd64-stable@39e5466df9-20260331T0716Z.build-manifest
INFO: Last successful auto-update of the UDD mirror: 2026-03-31 10:05:02+00:00 (0:03:02.033046 ago)
INFO: Need to upgrade to a new APT snapshot:
  - firmware-nonfree (20260221-1) to Debian forky (20260309-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: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
Feature: Thunderbird email client
Tags: @product @check_tor_leaks
2:8.333
Scenario I can send emails, and receive emails over IMAP
Steps
When I enter my email credentials into the autoconfiguration wizard 2:8.333
try_for() 
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/thunderbird.rb:106:in `/^I enter my email credentials into the autoconfiguration wizard$/'
features/thunderbird.feature:20:in `When I enter my email credentials into the autoconfiguration wizard'
Then the autoconfiguration wizard's choice for the incoming server is secure IMAP 0.000
And the autoconfiguration wizard's choice for the outgoing server is secure SMTP 0.000
When I accept the autoconfiguration wizard's configuration 0.000
And I send an email to myself 0.000
And I fetch my email 0.000
Then I can find the email I sent to myself in my inbox 0.000
And the only connections have been made to my email server 0.000
After features/support/hooks.rb:527 0.041
After features/support/hooks.rb:331 7.852 
SCENARIO FAILED: 'I can send emails, and receive emails over IMAP' (at time 03:02:54)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6250/artifact/build-artifacts/03:02:54_I_can_send_emails,_and_receive_emails_over_IMAP.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6250/artifact/build-artifacts/03:02:54_I_can_send_emails,_and_receive_emails_over_IMAP.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6250/artifact/build-artifacts/03:02:54_I_can_send_emails,_and_receive_emails_over_IMAP.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6250/artifact/build-artifacts/03:02:54_I_can_send_emails,_and_receive_emails_over_IMAP.journal
After features/support/hooks.rb:100 0.000