Project Number Date
test_Tails_ISO_stable 6564 06 Aug 2026, 12:59

Failures Overview

The following summary displays scenarios that failed.

Feature: Using Tor bridges and pluggable transports
Tags: @product
4:36.352
Scenario Asking for mocked bridge settings with automatic region-detection in Tor Connection
Steps
Given the Moat distributor responds with the default bridges 0.258
When I configure Tor Connection to ask for bridge settings based on my location 6.093
And I wait until Tor is ready 4:30.000
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:261:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:713:in `/^I wait( for a long time)? until Tor is ready$/'
features/tor_bridges.feature:104:in `And I wait until Tor is ready'
And available upgrades have been checked 0.000
Then Tor is configured to use the default bridges 0.000
And all Internet traffic has only flowed through the default bridges or connectivity check service 0.000
After features/support/hooks.rb:339 5.246 
SCENARIO FAILED: 'Asking for mocked bridge settings with automatic region-detection in Tor Connection' (at time 00:31:48)
Failed to copy Chutney data: No such file or directory @ rb_file_s_lstat - /tmp/TailsToaster/chutney-data/nodes.1786006612/012relay/diff-cache/1035
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6564/artifact/build-artifacts/00:31:48_Asking_for_mocked_bridge_settings_with_automatic_region-detection_in_Tor_Connection_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6564/artifact/build-artifacts/00:31:48_Asking_for_mocked_bridge_settings_with_automatic_region-detection_in_Tor_Connection.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6564/artifact/build-artifacts/00:31:48_Asking_for_mocked_bridge_settings_with_automatic_region-detection_in_Tor_Connection.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6564/artifact/build-artifacts/00:31:48_Asking_for_mocked_bridge_settings_with_automatic_region-detection_in_Tor_Connection.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6564/artifact/build-artifacts/00:31:48_Asking_for_mocked_bridge_settings_with_automatic_region-detection_in_Tor_Connection.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6564/artifact/build-artifacts/00:31:48_Asking_for_mocked_bridge_settings_with_automatic_region-detection_in_Tor_Connection.journal
After features/support/hooks.rb:108 0.040
Feature: Upgrading an old Tails USB installation
Tags: @product
1:54.747
Scenario Upgrading an old Tails USB installation from another Tails USB drive
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Steps
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 8.423
And I log in to a new session 11.140
And I clone USB drive "old" to a new USB drive "to_upgrade" 0.793
And I plug USB drive "to_upgrade" 2.256
When I upgrade Tails to USB drive "to_upgrade" by cloning 1:31.294
Then the running Tails is installed on USB drive "to_upgrade" 0.839
Command 
Command failed: udisksctl info --block-device '/dev/sdb1'
error code: 1
stdout: 
stderr: Error looking up object for device /dev/sdb1
.
<false> is not true. (ExecutionFailedInVM)
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/usb.rb:548:in `check_part_integrity'
./features/step_definitions/usb.rb:572:in `tails_is_installed_helper'
./features/step_definitions/usb.rb:610:in `/^the running Tails is installed on USB drive "([^"]+)"$/'
features/usb_upgrade.feature:66:in `Then the running Tails is installed on USB drive "to_upgrade"'
And I unplug USB drive "to_upgrade" 0.000
And I unplug USB drive "__internal" 0.000
After features/support/hooks.rb:339 5.393 
SCENARIO FAILED: 'Upgrading an old Tails USB installation from another Tails USB drive' (at time 01:17:03)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6564/artifact/build-artifacts/01:17:03_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6564/artifact/build-artifacts/01:17:03_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6564/artifact/build-artifacts/01:17:03_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6564/artifact/build-artifacts/01:17:03_Upgrading_an_old_Tails_USB_installation_from_another_Tails_USB_drive.journal
After features/support/hooks.rb:108 0.000
Feature: Packages are up-to-date
Tags: @source @fragile
4.824
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.824
Command 
Command failed (pid 117725 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-7.10.1.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_stable/tmp/tails-amd64-7.10.1.build-manifest
INFO: Last successful auto-update of the UDD mirror: 2026-08-06 10:05:02+00:00 (1:21:17.888034 ago)
INFO: Need to upgrade to a new APT snapshot:
  - aom (3.12.1-1) to Debian trixie-security (3.12.1-1+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:559 0.000
After features/support/hooks.rb:108 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
1:23.223
Scenario WebRTC is disabled in Tor Browser
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Steps
Given I have started Tails from DVD and logged in and the network is connected 9.255
When I start the Tor Browser 7.525
When I open the address "https://net.ipcalf.com/" in the Tor Browser 6.443
Then Tor Browser displays a 'ifconfig | grep inet | grep -v inet6 | cut -d" " -f2 | tail -n1' heading on the "Network IP Address via ipcalf.com" page 1:0.000
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/browser.rb:405:in `/^Tor Browser displays a '([^']+)' heading on the "([^"]+)" page$/'
features/torified_browsing.feature:97:in `Then Tor Browser displays a 'ifconfig | grep inet | grep -v inet6 | cut -d" " -f2 | tail -n1' heading on the "Network IP Address via ipcalf.com" page'
When I open the address "https://mozilla.github.io/webrtc-landing/pc_test.html" in the Tor Browser 0.000
Then Tor Browser displays a "RTCPeerConnection is missing!" heading on the "Simple RTCPeerConnection Video Test" page 0.000
After features/support/hooks.rb:339 5.368 
SCENARIO FAILED: 'WebRTC is disabled in Tor Browser' (at time 03:38:45)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6564/artifact/build-artifacts/03:38:45_WebRTC_is_disabled_in_Tor_Browser.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6564/artifact/build-artifacts/03:38:45_WebRTC_is_disabled_in_Tor_Browser.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6564/artifact/build-artifacts/03:38:45_WebRTC_is_disabled_in_Tor_Browser.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/6564/artifact/build-artifacts/03:38:45_WebRTC_is_disabled_in_Tor_Browser.journal
After features/support/hooks.rb:108 0.000