Project Number Date
test_Tails_ISO_devel 4636 25 Sep 2026, 12:15

Failures Overview

The following summary displays scenarios that failed.

Feature: Installing and running Flatpak apps in Tails
Tags: @product @check_tor_leaks
5:25.106
Scenario Installing, starting and uninstalling a Flatpak
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 I have started Tails with the Flatpak feature from a USB drive with a persistent partition enabled and logged in and the network is connected 5:25.106
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\ with\ the\ Flatpak\ feature\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in\ and\ the\ network\ is\ connected$/'
features/flatpak.feature:25:in `Given I have started Tails with the Flatpak feature from a USB drive with a persistent partition enabled and logged in and the network is connected'
When I start GNOME Software 0.000
And I install Signal Desktop using GNOME Software 0.000
Then the org.signal.Signal Flatpak is installed after at most 600 seconds 0.000
When I start the org.signal.Signal Flatpak 0.000
Then the org.signal.Signal Flatpak is running 0.000
Given I kill the org.signal.Signal Flatpak 0.000
And I go to the main screen of GNOME Software 0.000
When I uninstall Signal Desktop using GNOME Software 0.000
Then the org.signal.Signal Flatpak is uninstalled after at most 60 seconds 0.000
After features/support/hooks.rb:535 0.038
After features/support/hooks.rb:339 4.744 
SCENARIO FAILED: 'Installing, starting and uninstalling a Flatpak' (at time 00:13:07)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_devel/4636/artifact/build-artifacts/00:13:07_Installing,_starting_and_uninstalling_a_Flatpak.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_devel/4636/artifact/build-artifacts/00:13:07_Installing,_starting_and_uninstalling_a_Flatpak.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_devel/4636/artifact/build-artifacts/00:13:07_Installing,_starting_and_uninstalling_a_Flatpak.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_devel/4636/artifact/build-artifacts/00:13:07_Installing,_starting_and_uninstalling_a_Flatpak.journal
After features/support/hooks.rb:108 0.007
Feature: Using Tor bridges and pluggable transports
Tags: @product
5:12.028
Scenario Using obfs4 pluggable transports
Steps
When I configure some obfs4 bridges in the Tor Connection Assistant in hide mode 9.956
Then I wait until Tor is ready 2.066
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 4.865 
SCENARIO FAILED: 'Using obfs4 pluggable transports' (at time 00:34:07)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_devel/4636/artifact/build-artifacts/00:34:07_Using_obfs4_pluggable_transports.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_devel/4636/artifact/build-artifacts/00:34:07_Using_obfs4_pluggable_transports.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_devel/4636/artifact/build-artifacts/00:34:07_Using_obfs4_pluggable_transports.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_devel/4636/artifact/build-artifacts/00:34:07_Using_obfs4_pluggable_transports.journal
After features/support/hooks.rb:108 0.043
Feature: Using Tor bridges and pluggable transports
Tags: @product
5:11.749
Scenario Asking for mocked bridge settings with automatic region-detection in Tor Connection
Steps
Given the Moat distributor responds with the default bridges 0.149
When I configure Tor Connection to ask for bridge settings based on my location 5.658
And I wait until Tor is ready 5.935
And available upgrades have been checked 5:0.006
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.913 
SCENARIO FAILED: 'Asking for mocked bridge settings with automatic region-detection in Tor Connection' (at time 00:44:39)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_devel/4636/artifact/build-artifacts/00:44:39_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/4636/artifact/build-artifacts/00:44:39_Asking_for_mocked_bridge_settings_with_automatic_region-detection_in_Tor_Connection.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_devel/4636/artifact/build-artifacts/00:44:39_Asking_for_mocked_bridge_settings_with_automatic_region-detection_in_Tor_Connection.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_devel/4636/artifact/build-artifacts/00:44:39_Asking_for_mocked_bridge_settings_with_automatic_region-detection_in_Tor_Connection.journal
After features/support/hooks.rb:108 0.047
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
6:13.406
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.084
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 6:13.322
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.040
After features/support/hooks.rb:339 5.121 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:23:21)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_devel/4636/artifact/build-artifacts/01:23:21_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/4636/artifact/build-artifacts/01:23:21_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/4636/artifact/build-artifacts/01:23:21_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/4636/artifact/build-artifacts/01:23:21_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/4636/artifact/build-artifacts/01:23:21_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/4636/artifact/build-artifacts/01:23:21_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/4636/artifact/build-artifacts/01:23:21_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/4636/artifact/build-artifacts/01:23:21_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/4636/artifact/build-artifacts/01:23:21_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.006
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited
5:51.281
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.002
Steps
Given a computer 0.078
And I start Tails from USB drive "__internal" with network unplugged 31.625
And I enable persistence 11.152
And I remove the "cowsay" deb files from the APT cache 0.040
And I log in to a new session 6.811
Then I see the "The installation of your additional software failed" notification after at most 300 seconds 5:1.572
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.044
After features/support/hooks.rb:339 10.039 
SCENARIO FAILED: 'I am notified when Additional Software fails to install a package' (at time 01:29:17)
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_devel/4636/artifact/build-artifacts/01:29:17_I_am_notified_when_Additional_Software_fails_to_install_a_package.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_devel/4636/artifact/build-artifacts/01:29:17_I_am_notified_when_Additional_Software_fails_to_install_a_package.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_devel/4636/artifact/build-artifacts/01:29:17_I_am_notified_when_Additional_Software_fails_to_install_a_package.journal
After features/support/hooks.rb:108 0.005
Feature: Emergency shutdown
Tags: @product @not_release_blocker
5:21.461
Scenario Tails shuts down on DVD boot medium removal
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 5:21.461
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\ and\ the\ network\ is\ connected$/'
features/emergency_shutdown.feature:12:in `Given I have started Tails from DVD and logged in and the network is connected'
When I eject the boot medium 0.000
Then Tails eventually shuts down 0.000
After features/support/hooks.rb:339 4.915 
SCENARIO FAILED: 'Tails shuts down on DVD boot medium removal' (at time 01:45:50)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_devel/4636/artifact/build-artifacts/01:45:50_Tails_shuts_down_on_DVD_boot_medium_removal.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_devel/4636/artifact/build-artifacts/01:45:50_Tails_shuts_down_on_DVD_boot_medium_removal.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_devel/4636/artifact/build-artifacts/01:45:50_Tails_shuts_down_on_DVD_boot_medium_removal.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_devel/4636/artifact/build-artifacts/01:45:50_Tails_shuts_down_on_DVD_boot_medium_removal.journal
After features/support/hooks.rb:108 0.000
Feature: Tails documentation
Tags: @product @doc @not_release_blocker
5:22.907
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 5:22.907
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\ and\ the\ network\ is\ connected$/'
features/documentation.feature:11:in `Given I have started Tails from DVD and logged in and the network is connected'
When I start "Tails Documentation" via GNOME Activities Overview 0.000
Then the Tor Browser has started 0.000
And "Tails - Documentation" has loaded in the Tor Browser 0.000
After features/support/hooks.rb:339 4.984 
SCENARIO FAILED: 'The Tails documentation launcher works when online' (at time 01:58:55)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_devel/4636/artifact/build-artifacts/01:58:55_The_Tails_documentation_launcher_works_when_online.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_devel/4636/artifact/build-artifacts/01:58:55_The_Tails_documentation_launcher_works_when_online.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_devel/4636/artifact/build-artifacts/01:58:55_The_Tails_documentation_launcher_works_when_online.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_devel/4636/artifact/build-artifacts/01:58:55_The_Tails_documentation_launcher_works_when_online.journal
After features/support/hooks.rb:108 0.000
Feature: Onion Circuits
Tags: @product
5:22.742
Scenario Onion Circuits shows some circuits
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 5:22.742
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\ and\ the\ network\ is\ connected$/'
features/onioncircuits.feature:5:in `Given I have started Tails from DVD and logged in and the network is connected'
When I start "Onion Circuits" via GNOME Activities Overview 0.000
Then Onion Circuits starts 0.000
And Onion Circuits shows some circuits 0.000
After features/support/hooks.rb:339 4.590 
SCENARIO FAILED: 'Onion Circuits shows some circuits' (at time 02:54:15)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_devel/4636/artifact/build-artifacts/02:54:15_Onion_Circuits_shows_some_circuits.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_devel/4636/artifact/build-artifacts/02:54:15_Onion_Circuits_shows_some_circuits.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_devel/4636/artifact/build-artifacts/02:54:15_Onion_Circuits_shows_some_circuits.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_devel/4636/artifact/build-artifacts/02:54:15_Onion_Circuits_shows_some_circuits.journal
After features/support/hooks.rb:108 0.000
Feature: Tails persistence
Tags: @product
6:4.442
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:4.442
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.931 
SCENARIO FAILED: 'Tails Persistent Storage behave tests' (at time 03:00:24)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_devel/4636/artifact/build-artifacts/03:00:24_Tails_Persistent_Storage_behave_tests.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_devel/4636/artifact/build-artifacts/03:00:24_Tails_Persistent_Storage_behave_tests.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_devel/4636/artifact/build-artifacts/03:00:24_Tails_Persistent_Storage_behave_tests.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_devel/4636/artifact/build-artifacts/03:00:24_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:22.793
Scenario Chatting with some friend over XMPP
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 I have started Tails from DVD and logged in and the network is connected 5:22.793
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\ and\ the\ network\ is\ connected$/'
features/pidgin.feature:17:in `Given I have started Tails from DVD and logged in and the network is connected'
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
Given my XMPP friend goes online 0.000
When I start a conversation with my friend 0.000
And I say something to my friend 0.000
Then I receive a response from my friend 0.000
After features/support/hooks.rb:535 0.033
After features/support/hooks.rb:339 4.966 
SCENARIO FAILED: 'Chatting with some friend over XMPP' (at time 03:31:06)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_devel/4636/artifact/build-artifacts/03:31:06_Chatting_with_some_friend_over_XMPP.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_devel/4636/artifact/build-artifacts/03:31:06_Chatting_with_some_friend_over_XMPP.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_devel/4636/artifact/build-artifacts/03:31:06_Chatting_with_some_friend_over_XMPP.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_devel/4636/artifact/build-artifacts/03:31:06_Chatting_with_some_friend_over_XMPP.journal
After features/support/hooks.rb:108 0.000
Feature: Tails has a sane default configuration
Tags: @product @not_release_blocker
5:21.654
Scenario No unexpected network services
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 5:21.654
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\ and\ the\ network\ is\ connected$/'
features/sane_defaults.feature:13:in `Given I have started Tails from DVD and logged in and the network is connected'
Then no unexpected services are listening for network connections 0.000
After features/support/hooks.rb:339 4.684 
SCENARIO FAILED: 'No unexpected network services' (at time 03:41:22)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_devel/4636/artifact/build-artifacts/03:41:22_No_unexpected_network_services.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_devel/4636/artifact/build-artifacts/03:41:22_No_unexpected_network_services.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_devel/4636/artifact/build-artifacts/03:41:22_No_unexpected_network_services.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_devel/4636/artifact/build-artifacts/03:41:22_No_unexpected_network_services.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.046
Scenario tails-upgrade-frontend-wrapper is using the Tails-specific SocksPort
Steps
When I monitor the network connections of tails-upgrade-frontend-wrapper 0.042
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.378 
SCENARIO FAILED: 'tails-upgrade-frontend-wrapper is using the Tails-specific SocksPort' (at time 04:25:42)
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_devel/4636/artifact/build-artifacts/04:25:42_tails-upgrade-frontend-wrapper_is_using_the_Tails-specific_SocksPort.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_devel/4636/artifact/build-artifacts/04:25:42_tails-upgrade-frontend-wrapper_is_using_the_Tails-specific_SocksPort.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_devel/4636/artifact/build-artifacts/04:25:42_tails-upgrade-frontend-wrapper_is_using_the_Tails-specific_SocksPort.journal
After features/support/hooks.rb:108 0.000