Project Number Date
test_Tails_ISO_stable 6695 27 Sep 2026, 12:17

Failures Overview

The following summary displays scenarios that failed.

Feature: Using Tor bridges and pluggable transports
Tags: @product
5:12.589
Scenario Using normal bridges
Steps
When I configure some normal bridges in the Tor Connection Assistant 11.474
Then I wait until Tor is ready 1.109
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: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.707 
SCENARIO FAILED: 'Using normal bridges' (at time 00:28:57)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/00:28:57_Using_normal_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/00:28:57_Using_normal_bridges.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/00:28:57_Using_normal_bridges.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/00:28:57_Using_normal_bridges.journal
After features/support/hooks.rb:108 0.029
Feature: Using Tor bridges and pluggable transports
Tags: @product
5:29.665
Scenario The same Tor configuration is applied when the network is reconnected
Steps
Given I configure a direct connection in the Tor Connection Assistant 5.396
And I wait until Tor is ready 1.747
When I disconnect the network through GNOME 10.399
And I connect the network through GNOME 9.916
Then the Tor Connection Assistant autostarts 0.067
And the Tor Connection Assistant connects to Tor 1.347
And I wait until Tor is ready 0.788
And Tor is using the same configuration as before 0.000
And available upgrades have been checked 5:0.002
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 5.208 
SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:37:44)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/00:37:44_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_stable/6695/artifact/build-artifacts/00:37:44_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/00:37:44_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/00:37:44_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal
After features/support/hooks.rb:108 0.032
Feature: Using Tor bridges and pluggable transports
Tags: @product
5:12.880
Scenario Asking for mocked bridge settings with automatic region-detection in Tor Connection
Steps
Given the Moat distributor responds with the default bridges 0.075
When I configure Tor Connection to ask for bridge settings based on my location 5.718
And I wait until Tor is ready 7.086
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 4.773 
SCENARIO FAILED: 'Asking for mocked bridge settings with automatic region-detection in Tor Connection' (at time 00:44:53)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/00:44:53_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_stable/6695/artifact/build-artifacts/00:44:53_Asking_for_mocked_bridge_settings_with_automatic_region-detection_in_Tor_Connection.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/00:44:53_Asking_for_mocked_bridge_settings_with_automatic_region-detection_in_Tor_Connection.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/00:44:53_Asking_for_mocked_bridge_settings_with_automatic_region-detection_in_Tor_Connection.journal
After features/support/hooks.rb:108 0.040
Feature: Additional software
Tags: @product @check_tor_leaks @slow
5:44.061
Scenario I set up Additional Software when installing a package without persistent partition and the package is installed next time I start Tails
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 start Tails from a freshly installed USB drive with an administration password and the network is plugged and I login 5:44.061
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:273:in `/^I start Tails from a freshly installed USB drive with an administration password and the network is plugged and I login$/'
features/additional_software_packages.feature:28:in `Given I start Tails from a freshly installed USB drive with an administration password and the network is plugged and I login'
And I update the APT lists using apt 0.000
And I install "popularity-contest" using apt 0.000
Then I am proposed to add the "popularity-contest" package to my Additional Software 0.000
When I create a persistent storage and activate the Additional Software feature 0.000
Then Additional Software is correctly configured for package "popularity-contest" 0.000
When 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
And I log in to a new session 0.000
And the Additional Software installation service has started 0.000
Then I am notified that the installation succeeded 0.000
And Additional Software is correctly configured for package "popularity-contest" 0.000
And the package "popularity-contest" is installed after Additional Software has been installed 0.000
After features/support/hooks.rb:535 0.036
After features/support/hooks.rb:339 5.032 
SCENARIO FAILED: 'I set up Additional Software when installing a package without persistent partition and the package is installed next time I start Tails' (at time 01:16:18)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/01:16:18_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.file_content_var_log_boot.log
Content of /run/live-additional-software/log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/01:16:18_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.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_stable/6695/artifact/build-artifacts/01:16:18_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/01:16:18_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/01:16:18_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/01:16:18_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.cmd_output_mount
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/01:16:18_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/01:16:18_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/01:16:18_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.journal
After features/support/hooks.rb:108 0.000
Feature: Additional software
Tags: @product @check_tor_leaks @slow
2:17.393
Scenario The Additional Software dpkg hook notices when persistence is locked down while installing 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.086
And I start Tails from USB drive "__internal" and I login with an administration password 1:4.341
And I update the APT lists using apt 7.700
When I install "ripgrep" using apt 3.139
Then the Additional Software dpkg hook has been run for package "ripgrep" and notices the persistence is locked 1:2.125
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/additional_software_packages.rb:153:in `/^the Additional Software dpkg hook has been run for package "([^"]*)" and notices the persistence is locked$/'
features/additional_software_packages.feature:49:in `Then the Additional Software dpkg hook has been run for package "ripgrep" and notices the persistence is locked'
And the package "ripgrep" is installed 0.000
After features/support/hooks.rb:535 0.048
After features/support/hooks.rb:339 5.259 
SCENARIO FAILED: 'The Additional Software dpkg hook notices when persistence is locked down while installing a package' (at time 01:18:41)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/01:18:41_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.file_content_var_log_boot.log
Content of /run/live-additional-software/log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/01:18:41_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.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_stable/6695/artifact/build-artifacts/01:18:41_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/01:18:41_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/01:18:41_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/01:18:41_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_mount
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/01:18:41_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/01:18:41_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/01:18:41_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.journal
After features/support/hooks.rb:108 0.009
Feature: Additional software
Tags: @product @check_tor_leaks @slow
46.846
Scenario My Additional Software list is configurable through a GUI or through notifications when I install or remove packages with APT or Synaptic
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Before features/support/hooks.rb:527 0.001
Steps
Given a computer 0.075
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 46.770
The 
The Dogtail init script raised: SearchError: descendant of [application | Welcome to Tails!]: child with roleName='password text'
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/usb.rb:698:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:729:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:245: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:55:in `And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password'
When I uninstall "popularity-contest" using apt 0.000
And I accept removing "popularity-contest" from Additional Software 0.000
Then "popularity-contest" is not in the list of Additional Software 0.000
When I start Synaptic 0.000
And I update the APT lists using Synaptic 0.000
And I install "cowsay" using Synaptic 0.000
And I accept adding "cowsay" to Additional Software 0.000
Then Additional Software is correctly configured for package "cowsay" 0.000
When I uninstall "cowsay" using apt 0.000
And I refuse removing "cowsay" from Additional Software 0.000
Then Additional Software is correctly configured for package "cowsay" 0.000
When I start "Additional Software" via GNOME Activities Overview 0.000
And I remove "cowsay" from the list of Additional Software using Additional Software GUI 0.000
Then "cowsay" is not in the list of Additional Software 0.000
When I install "cowsay" using apt 0.000
And I refuse adding "cowsay" to Additional Software 0.000
Then "cowsay" is not in the list of Additional Software 0.000
After features/support/hooks.rb:535 0.030
After features/support/hooks.rb:339 5.385 
SCENARIO FAILED: 'My Additional Software list is configurable through a GUI or through notifications when I install or remove packages with APT or Synaptic' (at time 01:19:33)
Exception thrown while trying to save /tmp/TailsToaster/artifact.file_content_run_live-additional-software_log: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/run/live-additional-software/log'
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/01:19:33_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.file_content_var_log_boot.log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/01:19:33_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/01:19:33_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/01:19:33_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/01:19:33_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.cmd_output_mount
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/01:19:33_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/01:19:33_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/01:19:33_My_Additional_Software_list_is_configurable_through_a_GUI_or_through_notifications_when_I_install_or_remove_packages_with_APT_or_Synaptic.journal
After features/support/hooks.rb:108 0.005
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
46.056
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.001
Before features/support/hooks.rb:527 0.001
Steps
Given a computer 0.090
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 45.966
The 
The Dogtail init script raised: SearchError: descendant of [application | Welcome to Tails!]: child with roleName='password text'
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/usb.rb:698:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:729:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:245: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 5.201 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:20:24)
Exception thrown while trying to save /tmp/TailsToaster/artifact.file_content_run_live-additional-software_log: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/run/live-additional-software/log'
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/01:20:24_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.file_content_var_log_boot.log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/01:20:24_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_stable/6695/artifact/build-artifacts/01:20:24_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_stable/6695/artifact/build-artifacts/01:20:24_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_stable/6695/artifact/build-artifacts/01:20:24_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_stable/6695/artifact/build-artifacts/01:20:24_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_stable/6695/artifact/build-artifacts/01:20:24_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_stable/6695/artifact/build-artifacts/01:20:24_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.043
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited
46.642
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.001
Before features/support/hooks.rb:527 0.001
Steps
Given a computer 0.079
And I start Tails from USB drive "__internal" with network unplugged 33.306
And I enable persistence 13.256
The 
The Dogtail init script raised: SearchError: descendant of [application | Welcome to Tails!]: child with roleName='password text'
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/usb.rb:698:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:729:in `/^I enable persistence( with the changed passphrase)?$/'
features/additional_software_packages.feature:123:in `And I enable persistence'
And I remove the "cowsay" deb files from the APT cache 0.000
And I log in to a new session 0.000
Then I see the "The installation of your additional software failed" notification after at most 300 seconds 0.000
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.044
After features/support/hooks.rb:339 4.929 
SCENARIO FAILED: 'I am notified when Additional Software fails to install a package' (at time 01:21:16)
Exception thrown while trying to save /tmp/TailsToaster/artifact.file_content_run_live-additional-software_log: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/run/live-additional-software/log'
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/01:21:16_I_am_notified_when_Additional_Software_fails_to_install_a_package.file_content_var_log_boot.log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/01:21:16_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/01:21:16_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/01:21:16_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/01:21:16_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_mount
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/01:21:16_I_am_notified_when_Additional_Software_fails_to_install_a_package.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/01:21:16_I_am_notified_when_Additional_Software_fails_to_install_a_package.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/01:21:16_I_am_notified_when_Additional_Software_fails_to_install_a_package.journal
After features/support/hooks.rb:108 0.005
Feature: Tails documentation
Tags: @product @doc @not_release_blocker
3:39.191
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 10.483
When I start "Tails Documentation" via GNOME Activities Overview 9.382
Then the Tor Browser has started 19.315
And "Tails - Documentation" has loaded in the Tor Browser 3:0.009
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 5.117 
SCENARIO FAILED: 'The Tails documentation launcher works when online' (at time 01:52:08)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/01:52:08_The_Tails_documentation_launcher_works_when_online.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/01:52:08_The_Tails_documentation_launcher_works_when_online.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/01:52:08_The_Tails_documentation_launcher_works_when_online.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/01:52:08_The_Tails_documentation_launcher_works_when_online.journal
After features/support/hooks.rb:108 0.000
Feature: Tails persistence
Tags: @product
6:7.098
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.098
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 4.875 
SCENARIO FAILED: 'Tails Persistent Storage behave tests' (at time 02:51:19)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/02:51:19_Tails_Persistent_Storage_behave_tests.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/02:51:19_Tails_Persistent_Storage_behave_tests.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/02:51:19_Tails_Persistent_Storage_behave_tests.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/02:51:19_Tails_Persistent_Storage_behave_tests.journal
After features/support/hooks.rb:108 0.000
Feature: Chatting anonymously using Pidgin
Tags: @product @fragile @check_tor_leaks
5:17.499
Scenario Using a persistent Pidgin configuration
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.002
Before features/support/hooks.rb:527 0.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.077
And the network is plugged 0.047
And Tor is ready 9.374
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.033
After features/support/hooks.rb:339 4.862 
SCENARIO FAILED: 'Using a persistent Pidgin configuration' (at time 03:25:21)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/03:25:21_Using_a_persistent_Pidgin_configuration.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/03:25:21_Using_a_persistent_Pidgin_configuration.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/03:25:21_Using_a_persistent_Pidgin_configuration.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/03:25:21_Using_a_persistent_Pidgin_configuration.journal
After features/support/hooks.rb:108 0.000
Feature: The Tor enforcement is effective
Tags: @product
9.609
Scenario Anti test: Detecting TCP leaks of DNS lookups with the firewall leak detector
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.324
And I capture all network traffic 0.003
And I disable Tails' firewall 0.104
When I do a TCP DNS lookup of "torproject.org" 0.176
Failed 
Failed to resolve torproject.org:
;; communications error to 9.9.9.9#53: connection reset
;; communications error to 9.9.9.9#53: connection reset
;; no servers could be reached
.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/firewall_leaks.rb:22:in `/^I do a TCP DNS lookup of "(.*?)"$/'
features/tor_enforcement.feature:28:in `When I do a TCP DNS lookup of "torproject.org"'
Then the firewall leak detector has detected leaks 0.000
After features/support/hooks.rb:339 4.823 
SCENARIO FAILED: 'Anti test: Detecting TCP leaks of DNS lookups with the firewall leak detector' (at time 03:50:25)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/03:50:25_Anti_test:_Detecting_TCP_leaks_of_DNS_lookups_with_the_firewall_leak_detector.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/03:50:25_Anti_test:_Detecting_TCP_leaks_of_DNS_lookups_with_the_firewall_leak_detector.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/03:50:25_Anti_test:_Detecting_TCP_leaks_of_DNS_lookups_with_the_firewall_leak_detector.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/03:50:25_Anti_test:_Detecting_TCP_leaks_of_DNS_lookups_with_the_firewall_leak_detector.journal
After features/support/hooks.rb:108 0.047
Feature: Tor stream isolation is effective
Tags: @product @check_tor_leaks @not_release_blocker
20:0.071
Scenario tails-upgrade-frontend-wrapper is using the Tails-specific SocksPort
Steps
When I monitor the network connections of tails-upgrade-frontend-wrapper 0.066
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.030
After features/support/hooks.rb:339 10.389 
SCENARIO FAILED: 'tails-upgrade-frontend-wrapper is using the Tails-specific SocksPort' (at time 04:12:22)
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/04:12:22_tails-upgrade-frontend-wrapper_is_using_the_Tails-specific_SocksPort.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/04:12:22_tails-upgrade-frontend-wrapper_is_using_the_Tails-specific_SocksPort.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/04:12:22_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
1:17.535
Scenario The Persistent directory is usable 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 without network from a USB drive with a persistent partition enabled and logged in 8.273
And the network is plugged 0.024
And I successfully configure Tor 9.296
And available upgrades have been checked 4.216
And all notifications have disappeared 7.864
And there is a GNOME bookmark for the Persistent directory 13.669
When I start the Tor Browser 9.479
And I download some file in the Tor Browser to the Persistent directory 24.709
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:109:in `And I download some file in the Tor Browser to the Persistent directory'
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 5.107 
SCENARIO FAILED: 'The Persistent directory is usable in Tor Browser' (at time 04:19:47)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/04:19:47_The_Persistent_directory_is_usable_in_Tor_Browser.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/04:19:47_The_Persistent_directory_is_usable_in_Tor_Browser.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/04:19:47_The_Persistent_directory_is_usable_in_Tor_Browser.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6695/artifact/build-artifacts/04:19:47_The_Persistent_directory_is_usable_in_Tor_Browser.journal
After features/support/hooks.rb:108 0.000