Project Number Date
test_Tails_ISO_devel 4638 27 Sep 2026, 11:54

Failures Overview

The following summary displays scenarios that failed.

Feature: Using Tor bridges and pluggable transports
Tags: @product
5:12.503
Scenario Using normal bridges
Steps
When I configure some normal bridges in the Tor Connection Assistant 9.391
Then I wait until Tor is ready 3.106
And tca.conf includes the configured bridges 0.004
And available upgrades have been checked 5: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/common_steps.rb:764:in `/^available upgrades have been checked$/'
features/tor_bridges.feature:17:in `And available upgrades have been checked'
And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.000
After features/support/hooks.rb:339 4.772 
SCENARIO FAILED: 'Using normal bridges' (at time 00:28:51)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_devel/4638/artifact/build-artifacts/00:28:51_Using_normal_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_devel/4638/artifact/build-artifacts/00:28:51_Using_normal_bridges.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_devel/4638/artifact/build-artifacts/00:28:51_Using_normal_bridges.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_devel/4638/artifact/build-artifacts/00:28:51_Using_normal_bridges.journal
After features/support/hooks.rb:108 0.030
Feature: Using Tor bridges and pluggable transports
Tags: @product
5:22.109
Scenario Fall back to default bridges if failing to connect directly to the Tor network
Steps
Given the Tor network is blocked 0.842
When I configure a direct connection in the Tor Connection Assistant 19.076
Then I wait until Tor is ready 2.185
And tca.conf includes no bridge 0.004
And available upgrades have been checked 5: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/common_steps.rb:764:in `/^available upgrades have been checked$/'
features/tor_bridges.feature:49:in `And available upgrades have been checked'
And 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 4.845 
SCENARIO FAILED: 'Fall back to default bridges if failing to connect directly to the Tor network' (at time 00:35:48)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_devel/4638/artifact/build-artifacts/00:35:48_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_devel/4638/artifact/build-artifacts/00:35:48_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_devel/4638/artifact/build-artifacts/00:35:48_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_devel/4638/artifact/build-artifacts/00:35:48_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.journal
After features/support/hooks.rb:108 0.038
Feature: Using Tor bridges and pluggable transports
Tags: @product
5:13.161
Scenario Asking for mocked bridge settings with automatic region-detection in Tor Connection
Steps
Given the Moat distributor responds with the default bridges 0.172
When I configure Tor Connection to ask for bridge settings based on my location 5.987
And I wait until Tor is ready 7.000
And available upgrades have been checked 5: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/common_steps.rb:764:in `/^available upgrades have been checked$/'
features/tor_bridges.feature:105:in `And available upgrades have been checked'
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.052 
SCENARIO FAILED: 'Asking for mocked bridge settings with automatic region-detection in Tor Connection' (at time 00:44:44)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_devel/4638/artifact/build-artifacts/00:44:44_Asking_for_mocked_bridge_settings_with_automatic_region-detection_in_Tor_Connection.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_devel/4638/artifact/build-artifacts/00:44:44_Asking_for_mocked_bridge_settings_with_automatic_region-detection_in_Tor_Connection.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_devel/4638/artifact/build-artifacts/00:44:44_Asking_for_mocked_bridge_settings_with_automatic_region-detection_in_Tor_Connection.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_devel/4638/artifact/build-artifacts/00:44:44_Asking_for_mocked_bridge_settings_with_automatic_region-detection_in_Tor_Connection.journal
After features/support/hooks.rb:108 0.056
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
7:42.157
Scenario Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Before features/support/hooks.rb:527 0.002
Steps
Given a computer 0.076
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 1:13.370
And I configure APT to prefer an old version of cowsay 0.005
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 8.146
And I accept adding "cowsay" to Additional Software 4.090
And Additional Software is correctly configured for package "cowsay" 0.633
And I shutdown Tails and wait for the computer to power off 3.865
And I start Tails from USB drive "__internal" with network unplugged 32.648
And I enable persistence 11.340
# We need to add back this custom APT source for the Additional Software
# install step, as it was not saved in persistence
And I configure APT to prefer an old version of cowsay 0.004
# Prevent the "Warning: virtual machine detected!" notification from racing
# with the one we'll be interacting with below.
And I disable the tails-virt-notify-user.service user unit 0.047
And I log in to a new session 7.399
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been installed 10.185
And I revert the APT tweaks that made it prefer an old version of cowsay 0.036
# We remove the newest package after it has been downloaded and before
# it is installed, so that the upgrade process fails
And I prepare the Additional Software upgrade process to fail 0.040
And the network is plugged 0.047
And Tor is ready 10.216
And available upgrades have been checked 5: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/common_steps.rb:764:in `/^available upgrades have been checked$/'
features/additional_software_packages.feature:101:in `And available upgrades have been checked'
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 0.000
And I can open the Additional Software configuration window from the notification 0.000
And I shutdown Tails and wait for the computer to power off 0.000
And I start Tails from USB drive "__internal" with network unplugged 0.000
And I enable persistence 0.000
# We need to add back this custom APT source for the Additional Software
# install step, as it was not saved in persistence
And I configure APT to prefer an old version of cowsay 0.000
And I log in to a new session 0.000
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been installed 0.000
And I revert the APT tweaks that made it prefer an old version of cowsay 0.000
And the network is plugged 0.000
And Tor is ready 0.000
Then the Additional Software upgrade service has started 0.000
And the installed version of package "cowsay" is newer than "3.03+dfsg2-1" 0.000
After features/support/hooks.rb:535 0.035
After features/support/hooks.rb:339 4.903 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:24:50)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_devel/4638/artifact/build-artifacts/01:24:50_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.file_content_var_log_boot.log
Content of /run/live-additional-software/log: https://jenkins.tails.net/job/test_Tails_ISO_devel/4638/artifact/build-artifacts/01:24:50_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.file_content_run_live-additional-software_log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.net/job/test_Tails_ISO_devel/4638/artifact/build-artifacts/01:24:50_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.net/job/test_Tails_ISO_devel/4638/artifact/build-artifacts/01:24:50_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.net/job/test_Tails_ISO_devel/4638/artifact/build-artifacts/01:24:50_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.net/job/test_Tails_ISO_devel/4638/artifact/build-artifacts/01:24:50_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.cmd_output_mount
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_devel/4638/artifact/build-artifacts/01:24:50_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_devel/4638/artifact/build-artifacts/01:24:50_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_devel/4638/artifact/build-artifacts/01:24:50_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.journal
After features/support/hooks.rb:108 0.018
Feature: Tails persistence
Tags: @product
6:7.919
Scenario Tails Persistent Storage behave tests
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 with an administration password and the network is connected 6:7.919
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/common_steps.rb:764:in `/^available upgrades have been checked$/'
./features/step_definitions/snapshots.rb:206:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:203:in `each'
./features/step_definitions/snapshots.rb:203:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:226:in `/^I\ have\ started\ Tails\ from\ DVD\ and\ logged\ in\ with\ an\ administration\ password\ and\ the\ network\ is\ connected$/'
features/persistence.feature:7:in `Given I have started Tails from DVD and logged in with an administration password and the network is connected'
And I update the APT lists using apt 0.000
And I install "python3-behave" using apt 0.000
Then the Tails Persistent Storage behave tests pass 0.000
After features/support/hooks.rb:339 5.183 
SCENARIO FAILED: 'Tails Persistent Storage behave tests' (at time 02:50:00)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_devel/4638/artifact/build-artifacts/02:50:00_Tails_Persistent_Storage_behave_tests.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_devel/4638/artifact/build-artifacts/02:50:00_Tails_Persistent_Storage_behave_tests.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_devel/4638/artifact/build-artifacts/02:50:00_Tails_Persistent_Storage_behave_tests.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_devel/4638/artifact/build-artifacts/02:50:00_Tails_Persistent_Storage_behave_tests.journal
After features/support/hooks.rb:108 0.000
Feature: Thunderbird email client
Tags: @product @check_tor_leaks
2:7.945
Scenario I can send emails, and receive emails over IMAP
Steps
When I enter my email credentials into the autoconfiguration wizard 2:7.945
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendant of [frame | Account Setup - Mozilla Thunderbird]: 'Done' button
STDOUT:

STDERR:


./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:272:in `button'
./features/step_definitions/thunderbird.rb:106: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/thunderbird.rb:106: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/thunderbird.rb:106:in `/^I enter my email credentials into the autoconfiguration wizard$/'
features/thunderbird.feature:21: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 system only established connections with my email server 0.000
After features/support/hooks.rb:535 0.055
After features/support/hooks.rb:339 11.001 
SCENARIO FAILED: 'I can send emails, and receive emails over IMAP' (at time 03:32:11)
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_devel/4638/artifact/build-artifacts/03:32:11_I_can_send_emails,_and_receive_emails_over_IMAP.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_devel/4638/artifact/build-artifacts/03:32:11_I_can_send_emails,_and_receive_emails_over_IMAP.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_devel/4638/artifact/build-artifacts/03:32:11_I_can_send_emails,_and_receive_emails_over_IMAP.journal
After features/support/hooks.rb:108 0.010
Feature: Tor stream isolation is effective
Tags: @product @check_tor_leaks @not_release_blocker
20:0.043
Scenario tails-upgrade-frontend-wrapper is using the Tails-specific SocksPort
Steps
When I monitor the network connections of tails-upgrade-frontend-wrapper 0.037
And I re-run tails-upgrade-frontend-wrapper 20:0.005
execution 
execution expired (RemoteShell::Timeout)
./features/support/helpers/remote_shell.rb:56:in `read'
./features/support/helpers/remote_shell.rb:56:in `block (3 levels) in communicate'
./features/support/helpers/remote_shell.rb:55:in `block (2 levels) in communicate'
<internal:kernel>:187:in `loop'
./features/support/helpers/remote_shell.rb:42:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb:124:in `execute'
./features/support/helpers/remote_shell.rb:135:in `initialize'
./features/support/helpers/vm_helper.rb:486:in `new'
./features/support/helpers/vm_helper.rb:486:in `execute'
./features/support/helpers/vm_helper.rb:492:in `execute_successfully'
./features/step_definitions/tor.rb:400:in `/^I re-run tails-upgrade-frontend-wrapper$/'
features/tor_stream_isolation.feature:24:in `And I re-run tails-upgrade-frontend-wrapper'
Then I see that tails-upgrade-frontend-wrapper is properly stream isolated 0.000
After features/support/hooks.rb:535 0.037
After features/support/hooks.rb:339 10.916 
SCENARIO FAILED: 'tails-upgrade-frontend-wrapper is using the Tails-specific SocksPort' (at time 04:08:59)
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_devel/4638/artifact/build-artifacts/04:08:59_tails-upgrade-frontend-wrapper_is_using_the_Tails-specific_SocksPort.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_devel/4638/artifact/build-artifacts/04:08:59_tails-upgrade-frontend-wrapper_is_using_the_Tails-specific_SocksPort.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_devel/4638/artifact/build-artifacts/04:08:59_tails-upgrade-frontend-wrapper_is_using_the_Tails-specific_SocksPort.journal
After features/support/hooks.rb:108 0.000