Project Number Date
test_Tails_ISO_stable 6446 15 Jun 2026, 14:42

Failures Overview

The following summary displays scenarios that failed.

Feature: Using Tor bridges and pluggable transports
Tags: @product
25.984
Scenario Asking for bridge settings but receiving a mocked API error in Tor Connection
Steps
Given the Moat distributor responds with an API error 0.026
When I configure Tor Connection to ask for bridge settings based on my location 5.954
Then the Tor Connection Assistant reports that it failed to connect 9.406
And the Tor Connection Assistant reports the Moat API error 10.596
The 
The Dogtail init script raised: SearchError: descendant of [application | Tor Connection]: child with name='Error code: moat_api_error' roleName='label'
STDOUT:

STDERR:

 (Dogtail::Failure)
./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/tor.rb:928:in `/^the Tor Connection Assistant reports the Moat API error$/'
features/tor_bridges.feature:113:in `And the Tor Connection Assistant reports the Moat API error'
After features/support/hooks.rb:339 5.288 
SCENARIO FAILED: 'Asking for bridge settings but receiving a mocked API error in Tor Connection' (at time 00:30:08)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6446/artifact/build-artifacts/00:30:08_Asking_for_bridge_settings_but_receiving_a_mocked_API_error_in_Tor_Connection.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6446/artifact/build-artifacts/00:30:08_Asking_for_bridge_settings_but_receiving_a_mocked_API_error_in_Tor_Connection.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6446/artifact/build-artifacts/00:30:08_Asking_for_bridge_settings_but_receiving_a_mocked_API_error_in_Tor_Connection.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6446/artifact/build-artifacts/00:30:08_Asking_for_bridge_settings_but_receiving_a_mocked_API_error_in_Tor_Connection.journal
After features/support/hooks.rb:108 0.047
Feature: Hardware failures
Tags: @product
1:9.142
Scenario Outline Disk partitioning errors without a persistent partition
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.020
Steps
Given a computer 0.208
And I set Tails to boot with options "test_partitioning_errors=fs_resize" 0.000
And I temporarily create a 7200 MiB disk named "temp" 0.077
And I plug USB drive "temp" 1.049
And I write the Tails USB image to disk "temp" 14.016
When I start Tails from USB drive "temp" with network unplugged 53.292
Then Tails is running from USB drive "temp" 0.497
<"usb"> 
<"usb"> expected but was
<"ata">. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:945:in `/^Tails is running from (.*) drive "([^"]+)"$/'
features/hardware_failure.feature:82:in `Then Tails is running from USB drive "temp"'
features/hardware_failure.feature:73:in `Then Tails is running from USB drive "temp"'
And the Greeter recommends reinstalling Tails due to partitioning errors 0.000
And the Greeter forbids starting Tails 0.000
And the Greeter forbids all settings but language 0.000
And Tails detected partitioning error fs-not-resized 0.000
After features/support/hooks.rb:339 4.733 
SCENARIO FAILED: 'Disk partitioning errors without a persistent partition, Examples (#3)' (at time 01:47:51)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6446/artifact/build-artifacts/01:47:51_Disk_partitioning_errors_without_a_persistent_partition,_Examples___3_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6446/artifact/build-artifacts/01:47:51_Disk_partitioning_errors_without_a_persistent_partition,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6446/artifact/build-artifacts/01:47:51_Disk_partitioning_errors_without_a_persistent_partition,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6446/artifact/build-artifacts/01:47:51_Disk_partitioning_errors_without_a_persistent_partition,_Examples___3_.journal
After features/support/hooks.rb:108 0.132
Feature: Packages are up-to-date
Tags: @source @fragile
2.668
Scenario All packages are up-to-date
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:552 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.668
Command 
Command failed (pid 136360 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@9a81eaa0c2-20260615T1008Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_stable/tmp/tails-amd64-stable@9a81eaa0c2-20260615T1008Z.build-manifest
INFO: Last successful auto-update of the UDD mirror: 2026-06-15 12:05:01+00:00 (0:56:29.544583 ago)
WARNING: tor-geoipdb: the package version (0.4.9.9-1~d13.trixie+1) is higher than the newest version in Debian (0.4.9.8-1)
WARNING: tor: the package version (0.4.9.9-1~d13.trixie+1) is higher than the newest version in Debian (0.4.9.8-1)
INFO: Need to upgrade to a new APT snapshot:
  - firmware-nonfree (20260410-1) to Debian trixie-backports (20260519-1~bpo13+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:13:in `Then all packages listed in the build manifest are up-to-date'
After features/support/hooks.rb:559 0.000
After features/support/hooks.rb:108 0.000