Project Number Date
test_Tails_ISO_stable-flatpak 56 25 Oct 2026, 19:42

Failures Overview

The following summary displays scenarios that failed.

Tags: @product
31.506
Scenario Tor Connection honors my choice of using default bridges on retry, too
Steps
Given the Tor network and default bridges are blocked 1.002
When I unsuccessfully configure some default bridges in the Tor Connection Assistant 21.030
Then the Tor Connection Assistant reports that it failed to connect 0.062
Given the Tor network and default bridges are unblocked 1.011
When I retry connecting to Tor 1.103
Then I wait until Tor is ready 6.572
And Tor is configured to use the default bridges 0.469
And all Internet traffic has only flowed through the default bridges or connectivity check service 0.253
tshark exited with error code 2.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/support/helpers/firewall_helper.rb:82:in `pcap_connections_helper'
./features/support/helpers/firewall_helper.rb:100:in `assert_all_connections'
./features/support/helpers/firewall_helper.rb:115:in `assert_no_leaks'
./features/step_definitions/tor.rb:1116:in `/^all Internet traffic has only flowed through (Tor|the \w+ bridges)( or (?:fake )?connectivity check service|)$/'
features/tor_bridges.feature:99:in `And all Internet traffic has only flowed through the default bridges or connectivity check service'
After features/support/hooks.rb:339 4.969

SCENARIO FAILED: 'Tor Connection honors my choice of using default bridges on retry, too' (at time 00:29:11)

Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/56/artifact/build-artifacts/00:29:11_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/56/artifact/build-artifacts/00:29:11_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.png

Video: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/56/artifact/build-artifacts/00:29:11_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.mkv

Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable-flatpak/56/artifact/build-artifacts/00:29:11_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.journal

After features/support/hooks.rb:108 0.042
4.846
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 4.846
Command failed (pid 75622 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_stable-flatpak/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_stable-flatpak/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_stable-flatpak/tmp/tails-amd64-stable@766c6d759f-20261025T1528Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_stable-flatpak/tmp/tails-amd64-stable@766c6d759f-20261025T1528Z.build-manifest
INFO: Last successful auto-update of the UDD mirror: 2026-10-25 18:05:02+00:00 (0:03:50.082616 ago)
INFO: Need to upgrade to a new APT snapshot:
  - firmware-sof (2026.09.1-1) to Debian sid (2026.09.2-1)
 (CommandFailed)
/var/lib/jenkins/workspace/test_Tails_ISO_stable-flatpak/features/support/helpers/misc_helpers.rb:332:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_stable-flatpak/features/support/helpers/misc_helpers.rb:319:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_stable-flatpak/features/support/helpers/misc_helpers.rb:319:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_stable-flatpak/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