Project Number Date
test_Tails_ISO_stable 6691 24 Sep 2026, 15:11

Failures Overview

The following summary displays scenarios that failed.

Feature: Using Tor bridges and pluggable transports
Tags: @product
5:12.590
Scenario Using normal bridges
Steps
When I configure some normal bridges in the Tor Connection Assistant 11.738
Then I wait until Tor is ready 0.846
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.665 
SCENARIO FAILED: 'Using normal bridges' (at time 00:31:55)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6691/artifact/build-artifacts/00:31:55_Using_normal_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable/6691/artifact/build-artifacts/00:31:55_Using_normal_bridges.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6691/artifact/build-artifacts/00:31:55_Using_normal_bridges.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6691/artifact/build-artifacts/00:31:55_Using_normal_bridges.journal
After features/support/hooks.rb:108 0.049
Feature: Using Tor bridges and pluggable transports
Tags: @product
5:30.547
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.510
Then I wait until Tor is ready 1.030
And tca.conf includes the configured bridges 0.006
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: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 5.038 
SCENARIO FAILED: 'Using obfs4 pluggable transports from a QR code' (at time 00:38:01)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6691/artifact/build-artifacts/00:38:01_Using_obfs4_pluggable_transports_from_a_QR_code.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable/6691/artifact/build-artifacts/00:38:01_Using_obfs4_pluggable_transports_from_a_QR_code.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6691/artifact/build-artifacts/00:38:01_Using_obfs4_pluggable_transports_from_a_QR_code.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6691/artifact/build-artifacts/00:38:01_Using_obfs4_pluggable_transports_from_a_QR_code.journal
After features/support/hooks.rb:108 0.058
Feature: Using Tor bridges and pluggable transports
Tags: @product @supports_real_tor
5:12.487
Scenario Default Tor bridges
Steps
When I configure the default bridges in the Tor Connection Assistant 10.925
Then I wait until Tor is ready 1.122
And Tor is configured to use the default bridges 0.433
And tca.conf includes no bridge 0.004
And available upgrades have been checked 5:0.000
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:764:in `/^available upgrades have been checked$/'
features/tor_bridges.feature: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.653 
SCENARIO FAILED: 'Default Tor bridges' (at time 00:43:26)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6691/artifact/build-artifacts/00:43:26_Default_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable/6691/artifact/build-artifacts/00:43:26_Default_Tor_bridges.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6691/artifact/build-artifacts/00:43:26_Default_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6691/artifact/build-artifacts/00:43:26_Default_Tor_bridges.journal
After features/support/hooks.rb:108 0.047
Feature: Using Tor bridges and pluggable transports
Tags: @product
5:20.600
Scenario Fall back to default bridges if failing to connect directly to the Tor network
Steps
Given the Tor network is blocked 1.192
When I configure a direct connection in the Tor Connection Assistant 18.434
Then I wait until Tor is ready 0.967
And tca.conf includes no bridge 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:49:in `And available upgrades have been checked'
And Tor is configured to use the default bridges 0.000
And all Internet traffic has only flowed through the default bridges or connectivity check service 0.000
After features/support/hooks.rb:339 5.130 
SCENARIO FAILED: 'Fall back to default bridges if failing to connect directly to the Tor network' (at time 00:49:00)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6691/artifact/build-artifacts/00:49:00_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable/6691/artifact/build-artifacts/00:49:00_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6691/artifact/build-artifacts/00:49:00_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6691/artifact/build-artifacts/00:49:00_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.journal
After features/support/hooks.rb:108 0.055
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker @fragile @doc
4:42.231
Scenario I am warned I can not use Additional Software when I start Tails from a DVD and install a package
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Before features/support/hooks.rb:527 0.001
Steps
Given I have started Tails from DVD and logged in with an administration password and the network is connected 1:23.252
And I update the APT lists using apt 7.362
When I install "popularity-contest" using apt 3.200
Then I am notified I can not use Additional Software for "popularity-contest" 3.166
And I can open the Additional Software documentation from the notification 3:5.248
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/step_definitions/additional_software_packages.rb:141:in `/^I can open the (.+) documentation from the notification$/'
features/additional_software_packages.feature:19:in `And I can open the Additional Software documentation from the notification'
After features/support/hooks.rb:535 0.039
After features/support/hooks.rb:339 5.681 
SCENARIO FAILED: 'I am warned I can not use Additional Software when I start Tails from a DVD and install a package' (at time 01:22:26)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6691/artifact/build-artifacts/01:22:26_I_am_warned_I_can_not_use_Additional_Software_when_I_start_Tails_from_a_DVD_and_install_a_package.file_content_var_log_boot.log
Content of /run/live-additional-software/log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6691/artifact/build-artifacts/01:22:26_I_am_warned_I_can_not_use_Additional_Software_when_I_start_Tails_from_a_DVD_and_install_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/6691/artifact/build-artifacts/01:22:26_I_am_warned_I_can_not_use_Additional_Software_when_I_start_Tails_from_a_DVD_and_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/6691/artifact/build-artifacts/01:22:26_I_am_warned_I_can_not_use_Additional_Software_when_I_start_Tails_from_a_DVD_and_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/6691/artifact/build-artifacts/01:22:26_I_am_warned_I_can_not_use_Additional_Software_when_I_start_Tails_from_a_DVD_and_install_a_package.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.net/job/test_Tails_ISO_stable/6691/artifact/build-artifacts/01:22:26_I_am_warned_I_can_not_use_Additional_Software_when_I_start_Tails_from_a_DVD_and_install_a_package.cmd_output_mount
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable/6691/artifact/build-artifacts/01:22:26_I_am_warned_I_can_not_use_Additional_Software_when_I_start_Tails_from_a_DVD_and_install_a_package.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6691/artifact/build-artifacts/01:22:26_I_am_warned_I_can_not_use_Additional_Software_when_I_start_Tails_from_a_DVD_and_install_a_package.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6691/artifact/build-artifacts/01:22:26_I_am_warned_I_can_not_use_Additional_Software_when_I_start_Tails_from_a_DVD_and_install_a_package.journal
After features/support/hooks.rb:108 0.002
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
6:20.128
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.177
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 6:19.951
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.030
After features/support/hooks.rb:339 5.095 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:36:07)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6691/artifact/build-artifacts/01:36:07_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_stable/6691/artifact/build-artifacts/01:36:07_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_stable/6691/artifact/build-artifacts/01:36:07_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/6691/artifact/build-artifacts/01:36:07_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/6691/artifact/build-artifacts/01:36:07_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/6691/artifact/build-artifacts/01:36:07_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/6691/artifact/build-artifacts/01:36:07_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/6691/artifact/build-artifacts/01:36:07_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/6691/artifact/build-artifacts/01:36:07_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.008
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited
5:58.330
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.002
Steps
Given a computer 0.086
And I start Tails from USB drive "__internal" with network unplugged 34.977
And I enable persistence 13.066
And I remove the "cowsay" deb files from the APT cache 0.058
And I log in to a new session 8.507
Then I see the "The installation of your additional software failed" notification after at most 300 seconds 5:1.633
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.041
After features/support/hooks.rb:339 5.031 
SCENARIO FAILED: 'I am notified when Additional Software fails to install a package' (at time 01:42:10)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6691/artifact/build-artifacts/01:42:10_I_am_notified_when_Additional_Software_fails_to_install_a_package.file_content_var_log_boot.log
Content of /run/live-additional-software/log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6691/artifact/build-artifacts/01:42:10_I_am_notified_when_Additional_Software_fails_to_install_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/6691/artifact/build-artifacts/01:42:10_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/6691/artifact/build-artifacts/01:42:10_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/6691/artifact/build-artifacts/01:42:10_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/6691/artifact/build-artifacts/01:42:10_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_mount
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable/6691/artifact/build-artifacts/01:42:10_I_am_notified_when_Additional_Software_fails_to_install_a_package.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6691/artifact/build-artifacts/01:42:10_I_am_notified_when_Additional_Software_fails_to_install_a_package.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6691/artifact/build-artifacts/01:42:10_I_am_notified_when_Additional_Software_fails_to_install_a_package.journal
After features/support/hooks.rb:108 0.007
Feature: Upgrading an old Tails USB installation
Tags: @product @automatic_upgrade
5:38.711
Scenario Upgrading an initial Tails installation with an incremental upgrade
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.649
And no SquashFS delta is installed 0.087
And Tails is fooled to think that version 6.0~testoverlayfs was initially installed 0.237
And Tails is fooled to think it is running version 6.0~testoverlayfs 0.063
And the file system changes introduced in version 6.2~testoverlayfs are not present 0.204
And the file system changes introduced in version 6.3~testoverlayfs are not present 0.362
When the network is plugged 0.040
And Tor is ready 12.830
Then I am proposed to install an incremental upgrade to version 6.2~testoverlayfs 1.029
And I can successfully install the incremental upgrade to version 6.2~testoverlayfs 5.050
Given I shutdown Tails and wait for the computer to power off 5.304
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:7.744
Then Tails is running version 6.2~testoverlayfs 0.008
And all tps features are active 8.538
And the file system changes introduced in version 6.2~testoverlayfs are present 0.174
And only the 6.2~testoverlayfs SquashFS delta is installed 0.101
# Our IUK sets a release date that can make Tor bootstrapping impossible
Given Tails system time is magically synchronized 0.109
# We'll really install Tails_amd64_6.0~testoverlayfs_to_6.3~testoverlayfs.iuk
# but we need some way to force upgrading a second time in a row
# even if only the initially installed version is considered
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.174
When the network is plugged 0.034
And Tor is ready 10.858
Then I am proposed to install an incremental upgrade to version 6.3~testoverlayfs 1.100
And I can successfully install the incremental upgrade to version 6.3~testoverlayfs 4.094
Given I shutdown Tails and wait for the computer to power off 3.867
When I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 1:5.663
Then Tails is running version 6.3~testoverlayfs 0.005
And all tps features are active 8.983
And the file system changes introduced in version 6.3~testoverlayfs are present 0.333
And only the 6.3~testoverlayfs SquashFS delta is installed 0.043
# Regression test for #17425 (i.e. the Upgrader would propose
# upgrading to the version that's already running)
Given Tails system time is magically synchronized 0.125
And Tails is fooled to think that version 6.1~testoverlayfs was initially installed 0.175
When the network is plugged 0.030
And Tor is ready 10.681
Then the Upgrader considers the system as up-to-date 2: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/usb.rb:1421:in `/^the Upgrader considers the system as up-to-date$/'
features/usb_upgrade.feature:120:in `Then the Upgrader considers the system as up-to-date'
# Regression test on #8158 (i.e. the IUK's filesystem is not part of the Unsafe Browser's chroot)
And I successfully start the Unsafe Browser 0.000
And the file system changes introduced in version 6.3~testoverlayfs are present in the Unsafe Browser's chroot 0.000
After features/support/hooks.rb:339 4.866 
SCENARIO FAILED: 'Upgrading an initial Tails installation with an incremental upgrade' (at time 01:55:42)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6691/artifact/build-artifacts/01:55:42_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable/6691/artifact/build-artifacts/01:55:42_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6691/artifact/build-artifacts/01:55:42_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6691/artifact/build-artifacts/01:55:42_Upgrading_an_initial_Tails_installation_with_an_incremental_upgrade.journal
After features/support/hooks.rb:108 0.028
Feature: Getting a DHCP lease without leaking too much information
5:24.290
Background
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Steps
Given I have started Tails from DVD without network and logged in 7.110
And I capture all network traffic 0.004
And the network is plugged 0.050
And Tor is ready 9.718
And all notifications have disappeared 7.407
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.607 
SCENARIO FAILED: 'Getting a DHCP lease with the default NetworkManager connection' (at time 02:09:11)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6691/artifact/build-artifacts/02:09:11_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable/6691/artifact/build-artifacts/02:09:11_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6691/artifact/build-artifacts/02:09:11_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6691/artifact/build-artifacts/02:09:11_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.journal
After features/support/hooks.rb:108 0.049
Feature: Tor stream isolation is effective
Tags: @product @check_tor_leaks
3:25.443
Scenario The Tor Browser is using the web browser-specific SocksPort
Steps
When I monitor the network connections of Tor Browser 0.044
And I start the Tor Browser 8.765
And I open the Tails homepage in the Tor Browser 16.574
Then the Tor Browser loads the Tails homepage 3:0.058
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/tor_stream_isolation.feature:31:in `Then the Tor Browser loads the Tails homepage'
And I see that Tor Browser is properly stream isolated 0.000
After features/support/hooks.rb:535 0.051
After features/support/hooks.rb:339 5.502 
SCENARIO FAILED: 'The Tor Browser is using the web browser-specific SocksPort' (at time 04:10:54)
Boot log: https://jenkins.tails.net/job/test_Tails_ISO_stable/6691/artifact/build-artifacts/04:10:54_The_Tor_Browser_is_using_the_web_browser-specific_SocksPort.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.net/job/test_Tails_ISO_stable/6691/artifact/build-artifacts/04:10:54_The_Tor_Browser_is_using_the_web_browser-specific_SocksPort.png
Video: https://jenkins.tails.net/job/test_Tails_ISO_stable/6691/artifact/build-artifacts/04:10:54_The_Tor_Browser_is_using_the_web_browser-specific_SocksPort.mkv
Systemd journal: https://jenkins.tails.net/job/test_Tails_ISO_stable/6691/artifact/build-artifacts/04:10:54_The_Tor_Browser_is_using_the_web_browser-specific_SocksPort.journal
After features/support/hooks.rb:108 0.000