Project Number Date
test_Tails_ISO_21790-tor-0.4.9.13 3 26 Sep 2026, 08:57

Failures Overview

The following summary displays scenarios that failed.

Feature: Using Tor bridges and pluggable transports
Tags: @product
5:11.808
Scenario Using obfs4 pluggable transports
Steps
When I configure some obfs4 bridges in the Tor Connection Assistant in hide mode 9.624
Then I wait until Tor is ready 2.178
And tca.conf includes the configured bridges 0.005
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:24:in `And available upgrades have been checked'
And all Internet traffic has only flowed through the configured bridges 0.000
After features/support/hooks.rb:339 5.102 
SCENARIO FAILED: 'Using obfs4 pluggable transports' (at time 00:29:14)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/00:29:14_Using_obfs4_pluggable_transports.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/00:29:14_Using_obfs4_pluggable_transports.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/00:29:14_Using_obfs4_pluggable_transports.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/00:29:14_Using_obfs4_pluggable_transports.journal
After features/support/hooks.rb:108 0.055
Feature: Using Tor bridges and pluggable transports
Tags: @product
5:29.881
Scenario Using obfs4 pluggable transports from a QR code
Steps
When I configure some obfs4 bridges from a QR code in the Tor Connection Assistant in hide mode 29.062
Then I wait until Tor is ready 0.812
And tca.conf includes the configured bridges 0.004
And available upgrades have been checked 5:0.001
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:31:in `And available upgrades have been checked'
And all Internet traffic has only flowed through the configured bridges 0.000
After features/support/hooks.rb:339 4.625 
SCENARIO FAILED: 'Using obfs4 pluggable transports from a QR code' (at time 00:34:57)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/00:34:57_Using_obfs4_pluggable_transports_from_a_QR_code.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/00:34:57_Using_obfs4_pluggable_transports_from_a_QR_code.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/00:34:57_Using_obfs4_pluggable_transports_from_a_QR_code.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/00:34:57_Using_obfs4_pluggable_transports_from_a_QR_code.journal
After features/support/hooks.rb:108 0.037
Feature: Using Tor bridges and pluggable transports
Tags: @product @supports_real_tor
5:13.143
Scenario Default Tor bridges
Steps
When I configure the default bridges in the Tor Connection Assistant 11.855
Then I wait until Tor is ready 0.993
And Tor is configured to use the default bridges 0.288
And tca.conf includes no bridge 0.007
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:40: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.599 
SCENARIO FAILED: 'Default Tor bridges' (at time 00:40:24)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/00:40:24_Default_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/00:40:24_Default_Tor_bridges.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/00:40:24_Default_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/00:40:24_Default_Tor_bridges.journal
After features/support/hooks.rb:108 0.045
Feature: Using Tor bridges and pluggable transports
Tags: @product
5:23.216
Scenario The same Tor configuration is applied when the network is reconnected
Steps
Given I configure a direct connection in the Tor Connection Assistant 4.297
And I wait until Tor is ready 2.778
When I disconnect the network through GNOME 8.182
And I connect the network through GNOME 6.832
Then the Tor Connection Assistant autostarts 0.057
And the Tor Connection Assistant connects to Tor 0.217
And I wait until Tor is ready 0.849
And Tor is using the same configuration as before 0.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:80:in `And available upgrades have been checked'
And all Internet traffic has only flowed through Tor or connectivity check service 0.000
After features/support/hooks.rb:339 4.959 
SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:47:49)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/00:47:49_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/00:47:49_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/00:47:49_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/00:47:49_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal
After features/support/hooks.rb:108 0.040
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
6:16.768
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.003
Steps
Given a computer 0.081
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 6:16.687
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/common_steps.rb:259:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/additional_software_packages.feature:79:in `And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password'
And I configure APT to prefer an old version of cowsay 0.000
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 0.000
And I accept adding "cowsay" to Additional Software 0.000
And Additional Software is correctly configured for package "cowsay" 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
# 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.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
# 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.000
And the network is plugged 0.000
And Tor is ready 0.000
And available upgrades have been checked 0.000
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.041
After features/support/hooks.rb:339 4.887 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:28:38)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/01:28:38_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_21790-tor-0.4.9.13/3/artifact/build-artifacts/01:28:38_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_21790-tor-0.4.9.13/3/artifact/build-artifacts/01:28:38_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_21790-tor-0.4.9.13/3/artifact/build-artifacts/01:28:38_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_21790-tor-0.4.9.13/3/artifact/build-artifacts/01:28:38_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_21790-tor-0.4.9.13/3/artifact/build-artifacts/01:28:38_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_21790-tor-0.4.9.13/3/artifact/build-artifacts/01:28:38_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_21790-tor-0.4.9.13/3/artifact/build-artifacts/01:28:38_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_21790-tor-0.4.9.13/3/artifact/build-artifacts/01:28:38_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.009
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited
5:54.110
Scenario I am notified when Additional Software fails to install a package
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Before features/support/hooks.rb:527 0.001
Steps
Given a computer 0.085
And I start Tails from USB drive "__internal" with network unplugged 33.789
And I enable persistence 11.761
And I remove the "cowsay" deb files from the APT cache 0.039
And I log in to a new session 6.852
Then I see the "The installation of your additional software failed" notification after at most 300 seconds 5:1.581
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:650:in `wait_notification'
./features/step_definitions/common_steps.rb:637:in `/^I (don't )?see the "(.+)" notification(?: after at most (\d+) seconds)?$/'
features/additional_software_packages.feature:126:in `Then I see the "The installation of your additional software failed" notification after at most 300 seconds'
And I can open the Additional Software log file from the notification 0.000
And the package "cowsay" is not installed 0.000
After features/support/hooks.rb:535 0.028
After features/support/hooks.rb:339 9.729 
SCENARIO FAILED: 'I am notified when Additional Software fails to install a package' (at time 01:34:37)
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/01:34:37_I_am_notified_when_Additional_Software_fails_to_install_a_package.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/01:34:37_I_am_notified_when_Additional_Software_fails_to_install_a_package.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/01:34:37_I_am_notified_when_Additional_Software_fails_to_install_a_package.journal
After features/support/hooks.rb:108 0.019
Feature: Getting a DHCP lease without leaking too much information
5:23.219
Background
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Steps
Given I have started Tails from DVD without network and logged in 6.344
And I capture all network traffic 0.003
And the network is plugged 0.037
And Tor is ready 9.382
And all notifications have disappeared 7.450
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/dhcp.feature:14:in `And available upgrades have been checked'
Feature: Getting a DHCP lease without leaking too much information
Tags: @product
0.000
Scenario Getting a DHCP lease with the default NetworkManager connection
Steps
Then the hostname should not have been leaked on the network 0.000
After features/support/hooks.rb:339 4.688 
SCENARIO FAILED: 'Getting a DHCP lease with the default NetworkManager connection' (at time 01:58:30)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/01:58:30_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/01:58:30_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/01:58:30_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/01:58:30_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.journal
After features/support/hooks.rb:108 0.042
Feature: Tails documentation
Tags: @product @doc @not_release_blocker
3:28.721
Scenario The Tails documentation launcher works when online
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.374
When I start "Tails Documentation" via GNOME Activities Overview 9.204
Then the Tor Browser has started 10.124
And "Tails - Documentation" has loaded in the Tor Browser 3:0.017
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:263:in `page_has_loaded_in_the_tor_browser'
./features/step_definitions/browser.rb:278:in `/^"([^"]+)" has loaded in the Tor Browser$/'
features/documentation.feature:14:in `And "Tails - Documentation" has loaded in the Tor Browser'
After features/support/hooks.rb:339 4.907 
SCENARIO FAILED: 'The Tails documentation launcher works when online' (at time 02:02:58)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/02:02:58_The_Tails_documentation_launcher_works_when_online.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/02:02:58_The_Tails_documentation_launcher_works_when_online.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/02:02:58_The_Tails_documentation_launcher_works_when_online.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/02:02:58_The_Tails_documentation_launcher_works_when_online.journal
After features/support/hooks.rb:108 0.000
Feature: Chatting anonymously using Pidgin
Tags: @product @fragile @check_tor_leaks
5:18.819
Scenario Using a persistent Pidgin configuration
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.019
Before features/support/hooks.rb:527 0.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.650
And the network is plugged 0.050
And Tor is ready 10.117
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/pidgin.feature:33:in `And available upgrades have been checked'
And all notifications have disappeared 0.000
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 0.000
Then I see Pidgin's account manager window 0.000
When I create my XMPP account 0.000
And I close Pidgin's account manager window 0.000
Then Pidgin automatically enables my XMPP account 0.000
When I close Pidgin 0.000
And I take note of the configured Pidgin accounts 0.000
And I shutdown Tails and wait for the computer to power off 0.000
Given a computer 0.000
And I start Tails from USB drive "__internal" and I login with persistence enabled 0.000
And Pidgin has the expected persistent accounts configured 0.000
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 0.000
Then Pidgin automatically enables my XMPP account 0.000
After features/support/hooks.rb:535 0.036
After features/support/hooks.rb:339 5.227 
SCENARIO FAILED: 'Using a persistent Pidgin configuration' (at time 03:31:05)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/03:31:05_Using_a_persistent_Pidgin_configuration.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/03:31:05_Using_a_persistent_Pidgin_configuration.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/03:31:05_Using_a_persistent_Pidgin_configuration.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/03:31:05_Using_a_persistent_Pidgin_configuration.journal
After features/support/hooks.rb:108 0.000
Feature: Tor stream isolation is effective
Tags: @product @check_tor_leaks @not_release_blocker
20:0.048
Scenario tails-upgrade-frontend-wrapper is using the Tails-specific SocksPort
Steps
When I monitor the network connections of tails-upgrade-frontend-wrapper 0.044
And I re-run tails-upgrade-frontend-wrapper 20:0.004
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.032
After features/support/hooks.rb:339 10.842 
SCENARIO FAILED: 'tails-upgrade-frontend-wrapper is using the Tails-specific SocksPort' (at time 04:17:16)
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/04:17:16_tails-upgrade-frontend-wrapper_is_using_the_Tails-specific_SocksPort.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/04:17:16_tails-upgrade-frontend-wrapper_is_using_the_Tails-specific_SocksPort.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/04:17:16_tails-upgrade-frontend-wrapper_is_using_the_Tails-specific_SocksPort.journal
After features/support/hooks.rb:108 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product @check_tor_leaks
36.759
Scenario Downloading files with the Tor Browser
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Before features/support/hooks.rb:527 0.002
Steps
Given I have started Tails from DVD and logged in and the network is connected 9.575
When I start the Tor Browser 7.711
When I download some file in the Tor Browser to the Downloads directory 19.472
The 
The Dogtail init script raised: SearchError: descendant of [application | Firefox]: child with name='Opening tails-signing.key'
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/browser.rb:356:in `/^I download some file in the Tor Browser to the (.*) directory$/'
features/torified_browsing.feature:29:in `When I download some file in the Tor Browser to the Downloads directory'
Then the file is saved to the Downloads directory 0.000
After features/support/hooks.rb:535 0.034
After features/support/hooks.rb:339 5.411 
SCENARIO FAILED: 'Downloading files with the Tor Browser' (at time 04:19:36)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/04:19:36_Downloading_files_with_the_Tor_Browser.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/04:19:36_Downloading_files_with_the_Tor_Browser.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/04:19:36_Downloading_files_with_the_Tor_Browser.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/04:19:36_Downloading_files_with_the_Tor_Browser.journal
After features/support/hooks.rb:108 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
3:33.314
Scenario The Tor Browser's circuit view feature works as expected
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.373
When I start the Tor Browser 7.674
And I open the Tails homepage in the Tor Browser 16.106
Then the Tor Browser loads the Tails homepage 3:0.159
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:263:in `page_has_loaded_in_the_tor_browser'
./features/step_definitions/browser.rb:621:in `/^the Tor Browser loads the (Tails homepage|Tails GitLab)$/'
features/torified_browsing.feature:90:in `Then the Tor Browser loads the Tails homepage'
And Tor Browser's circuit view is working 0.000
After features/support/hooks.rb:339 5.478 
SCENARIO FAILED: 'The Tor Browser's circuit view feature works as expected' (at time 04:26:07)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/04:26:07_The_Tor_Browser_s_circuit_view_feature_works_as_expected.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/04:26:07_The_Tor_Browser_s_circuit_view_feature_works_as_expected.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/04:26:07_The_Tor_Browser_s_circuit_view_feature_works_as_expected.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/04:26:07_The_Tor_Browser_s_circuit_view_feature_works_as_expected.journal
After features/support/hooks.rb:108 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
5:21.684
Scenario The Persistent directory is usable in Tor Browser
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.602
And the network is plugged 0.041
And I successfully configure Tor 13.039
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/torified_browsing.feature:105:in `And available upgrades have been checked'
And all notifications have disappeared 0.000
And there is a GNOME bookmark for the Persistent directory 0.000
When I start the Tor Browser 0.000
And I download some file in the Tor Browser to the Persistent directory 0.000
Then the file is saved to the Persistent directory 0.000
When I open the address "https://tails.net/about" in the Tor Browser 0.000
Then "Tails - How Tails works" has loaded in the Tor Browser 0.000
And I can print the current page as "output.pdf" to the Persistent directory 0.000
After features/support/hooks.rb:339 4.745 
SCENARIO FAILED: 'The Persistent directory is usable in Tor Browser' (at time 04:32:06)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/04:32:06_The_Persistent_directory_is_usable_in_Tor_Browser.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/04:32:06_The_Persistent_directory_is_usable_in_Tor_Browser.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/04:32:06_The_Persistent_directory_is_usable_in_Tor_Browser.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_21790-tor-0.4.9.13/3/artifact/build-artifacts/04:32:06_The_Persistent_directory_is_usable_in_Tor_Browser.journal
After features/support/hooks.rb:108 0.000