Project Number Date
test_Tails_ISO_feature-arti 52 08 May 2025, 19:59

Failures Overview

The following summary displays scenarios that failed.

Feature: Time syncing
Tags: @product @check_tor_leaks
4:54.831
Scenario Clock with host's time while using bridges
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Before features/support/hooks.rb:507 0.002
Steps
Given I have started Tails from DVD without network and logged in 9.578
When the network is plugged 0.070
And the Tor Connection Assistant autostarts 3.477
And I configure some normal bridges in the Tor Connection Assistant 11.117
And I wait until Tor is ready 4:30.587
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/time_syncing.feature:18:in `And I wait until Tor is ready'
Then the system clock is less than 5 minutes incorrect 0.000
After features/support/hooks.rb:515 0.032
After features/support/hooks.rb:330 5.141 
SCENARIO FAILED: 'Clock with host's time while using bridges' (at time 00:17:07)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:17:07_Clock_with_host_s_time_while_using_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:17:07_Clock_with_host_s_time_while_using_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:17:07_Clock_with_host_s_time_while_using_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:17:07_Clock_with_host_s_time_while_using_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:17:07_Clock_with_host_s_time_while_using_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:17:07_Clock_with_host_s_time_while_using_bridges.journal
After features/support/hooks.rb:100 0.000
Feature: Time syncing
Tags: @product @check_tor_leaks
4:56.940
Scenario Clock is one day in the future while using obfs4 bridges
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Before features/support/hooks.rb:507 0.004
Steps
Given I have started Tails from DVD without network and logged in 8.453
When I bump the system time with "+1 day" 0.554
And I capture all network traffic 0.002
And the network is plugged 0.110
And the Tor Connection Assistant autostarts 3.986
And I configure some obfs4 bridges in the Tor Connection Assistant in easy mode 12.430
And I wait until Tor is ready 4:31.403
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/time_syncing.feature:28:in `And I wait until Tor is ready'
Then the system clock is less than 5 minutes incorrect 0.000
And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.000
After features/support/hooks.rb:515 0.034
After features/support/hooks.rb:330 5.335 
SCENARIO FAILED: 'Clock is one day in the future while using obfs4 bridges' (at time 00:22:09)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:22:09_Clock_is_one_day_in_the_future_while_using_obfs4_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:22:09_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:22:09_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:22:09_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:22:09_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:22:09_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.journal
After features/support/hooks.rb:100 0.035
Feature: Time syncing
Tags: @product @check_tor_leaks
5:26.077
Scenario I can manually recover from time sync failure when connecting automatically to obfs4 bridges with a clock East of UTC
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Before features/support/hooks.rb:507 0.002
Steps
Given I have started Tails from DVD without network and logged in 8.910
When I bump the system time with "+8 hours +15 minutes" 0.340
And all notifications have disappeared 4.367
And I capture all network traffic 0.003
And I make sure time sync before Tor connects fails 0.121
And the network is plugged 0.077
And the Tor Connection Assistant autostarts 3.376
When I configure the default bridges in the Tor Connection Assistant in easy mode without connecting 5.458
And I click "Connect to Tor" 1.173
And the Tor Connection Assistant fails to connect to Tor 15.830
# The "Fix Clock" button allows users to recover from this bug
Then I set the time zone in Tor Connection to "Asia/Shanghai" 14.901
Then the system clock is less than 20 minutes incorrect 0.235
When I click "Connect to Tor" 1.179
Then I wait until Tor is ready 4:30.100
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/time_syncing.feature:77:in `Then I wait until Tor is ready'
And all Internet traffic has only flowed through the default bridges or fake connectivity check service 0.000
# check that htpdate has done its job
And the system clock is less than 5 minutes incorrect 0.000
After features/support/hooks.rb:515 0.038
After features/support/hooks.rb:330 5.356 
SCENARIO FAILED: 'I can manually recover from time sync failure when connecting automatically to obfs4 bridges with a clock East of UTC' (at time 00:32:17)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:32:17_I_can_manually_recover_from_time_sync_failure_when_connecting_automatically_to_obfs4_bridges_with_a_clock_East_of_UTC_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:32:17_I_can_manually_recover_from_time_sync_failure_when_connecting_automatically_to_obfs4_bridges_with_a_clock_East_of_UTC.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:32:17_I_can_manually_recover_from_time_sync_failure_when_connecting_automatically_to_obfs4_bridges_with_a_clock_East_of_UTC.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:32:17_I_can_manually_recover_from_time_sync_failure_when_connecting_automatically_to_obfs4_bridges_with_a_clock_East_of_UTC.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:32:17_I_can_manually_recover_from_time_sync_failure_when_connecting_automatically_to_obfs4_bridges_with_a_clock_East_of_UTC.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:32:17_I_can_manually_recover_from_time_sync_failure_when_connecting_automatically_to_obfs4_bridges_with_a_clock_East_of_UTC.journal
After features/support/hooks.rb:100 0.062
Feature: Time syncing
Tags: @product @check_tor_leaks
5:22.319
Scenario I can connect to obfs4 bridges having a clock East of UTC while hiding that I am using Tor
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Before features/support/hooks.rb:507 0.002
Steps
Given I have started Tails from DVD without network and logged in 8.624
When I bump the system time with "+8 hours +15 minutes" 0.389
And all notifications have disappeared 4.502
And I capture all network traffic 0.004
And the network is plugged 0.073
And the Tor Connection Assistant autostarts 4.163
# Anti-test: Users east of UTC can't connect to obfs4 bridges
And I configure some obfs4 bridges in the Tor Connection Assistant in hide mode without connecting 4.349
And I click "Connect to Tor" 1.176
Then the Tor Connection Assistant reports that it failed to connect 11.848
# The "Fix Clock" button allows users to recover from this bug
When I set the time zone in Tor Connection to "Asia/Shanghai" 15.085
Then the system clock is less than 20 minutes incorrect 0.251
# "Asia/Shanghai" is UTC+08:00 all year long (no DST)
And the displayed clock is less than 20 minutes incorrect in "+08:00" 0.413
When I click "Connect to Tor" 1.179
Then I wait until Tor is ready 4:30.256
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/time_syncing.feature:99:in `Then I wait until Tor is ready'
And all Internet traffic has only flowed through the configured bridges 0.000
# check that htpdate has done its job
And the system clock is less than 5 minutes incorrect 0.000
And the displayed clock is less than 5 minutes incorrect in "+08:00" 0.000
After features/support/hooks.rb:515 0.039
After features/support/hooks.rb:330 5.310 
SCENARIO FAILED: 'I can connect to obfs4 bridges having a clock East of UTC while hiding that I am using Tor' (at time 00:37:45)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:37:45_I_can_connect_to_obfs4_bridges_having_a_clock_East_of_UTC_while_hiding_that_I_am_using_Tor_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:37:45_I_can_connect_to_obfs4_bridges_having_a_clock_East_of_UTC_while_hiding_that_I_am_using_Tor.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:37:45_I_can_connect_to_obfs4_bridges_having_a_clock_East_of_UTC_while_hiding_that_I_am_using_Tor.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:37:45_I_can_connect_to_obfs4_bridges_having_a_clock_East_of_UTC_while_hiding_that_I_am_using_Tor.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:37:45_I_can_connect_to_obfs4_bridges_having_a_clock_East_of_UTC_while_hiding_that_I_am_using_Tor.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:37:45_I_can_connect_to_obfs4_bridges_having_a_clock_East_of_UTC_while_hiding_that_I_am_using_Tor.journal
After features/support/hooks.rb:100 0.036
Feature: Using Tor bridges and pluggable transports
Tags: @product
4:43.611
Scenario Using normal bridges
Steps
When I configure some normal bridges in the Tor Connection Assistant 12.717
Then I wait until Tor is ready 4:30.894
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/tor_bridges.feature:15:in `Then I wait until Tor is ready'
And tca.conf includes the configured bridges 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.000
After features/support/hooks.rb:330 5.212 
SCENARIO FAILED: 'Using normal bridges' (at time 00:43:44)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:43:44_Using_normal_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:43:44_Using_normal_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:43:44_Using_normal_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:43:44_Using_normal_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:43:44_Using_normal_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:43:44_Using_normal_bridges.journal
After features/support/hooks.rb:100 0.034
Feature: Using Tor bridges and pluggable transports
Tags: @product
4:43.174
Scenario Using obfs4 pluggable transports
Steps
When I configure some obfs4 bridges in the Tor Connection Assistant in hide mode 12.114
Then I wait until Tor is ready 4:31.059
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/tor_bridges.feature:22:in `Then I wait until Tor is ready'
And tca.conf includes the configured bridges 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through the configured bridges 0.000
After features/support/hooks.rb:330 5.328 
SCENARIO FAILED: 'Using obfs4 pluggable transports' (at time 00:48:45)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:48:45_Using_obfs4_pluggable_transports_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:48:45_Using_obfs4_pluggable_transports.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:48:45_Using_obfs4_pluggable_transports.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:48:45_Using_obfs4_pluggable_transports.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:48:45_Using_obfs4_pluggable_transports.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:48:45_Using_obfs4_pluggable_transports.journal
After features/support/hooks.rb:100 0.062
Feature: Using Tor bridges and pluggable transports
Tags: @product
5:4.053
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 32.907
Then I wait until Tor is ready 4:31.146
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/tor_bridges.feature:29:in `Then I wait until Tor is ready'
And tca.conf includes the configured bridges 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through the configured bridges 0.000
After features/support/hooks.rb:330 5.314 
SCENARIO FAILED: 'Using obfs4 pluggable transports from a QR code' (at time 00:54:07)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:54:07_Using_obfs4_pluggable_transports_from_a_QR_code_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:54:07_Using_obfs4_pluggable_transports_from_a_QR_code.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:54:07_Using_obfs4_pluggable_transports_from_a_QR_code.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:54:07_Using_obfs4_pluggable_transports_from_a_QR_code.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:54:07_Using_obfs4_pluggable_transports_from_a_QR_code.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:54:07_Using_obfs4_pluggable_transports_from_a_QR_code.journal
After features/support/hooks.rb:100 0.061
Feature: Using Tor bridges and pluggable transports
Tags: @product
5:29.090
Scenario TCA can scan QR code after a connection failure
Steps
Given the Tor network and default bridges are blocked 1.618
When I unsuccessfully configure a direct connection in the Tor Connection Assistant 32.980
Then the Tor Connection Assistant reports that it failed to connect 0.124
And tca.conf is empty 0.301
Given I scan a QR code from the error page in Tor Connection Assistant 21.920
And I retry connecting to Tor 1.165
Then I wait until Tor is ready 4:30.980
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/tor_bridges.feature:41:in `Then I wait until Tor is ready'
And tca.conf includes the configured bridges 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.000
After features/support/hooks.rb:330 5.163 
SCENARIO FAILED: 'TCA can scan QR code after a connection failure' (at time 00:59:54)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:59:54_TCA_can_scan_QR_code_after_a_connection_failure_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:59:54_TCA_can_scan_QR_code_after_a_connection_failure.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:59:54_TCA_can_scan_QR_code_after_a_connection_failure.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:59:54_TCA_can_scan_QR_code_after_a_connection_failure.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:59:54_TCA_can_scan_QR_code_after_a_connection_failure.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/00:59:54_TCA_can_scan_QR_code_after_a_connection_failure.journal
After features/support/hooks.rb:100 0.041
Feature: Using Tor bridges and pluggable transports
Tags: @product @supports_real_tor
4:44.545
Scenario Default Tor bridges
Steps
When I configure the default bridges in the Tor Connection Assistant 13.593
Then I wait until Tor is ready 4:30.952
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/tor_bridges.feature:49:in `Then I wait until Tor is ready'
And Tor is configured to use the default bridges 0.000
And tca.conf includes no bridge 0.000
And available upgrades have been checked 0.000
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:330 5.392 
SCENARIO FAILED: 'Default Tor bridges' (at time 01:04:57)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/01:04:57_Default_Tor_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/01:04:57_Default_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/01:04:57_Default_Tor_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/01:04:57_Default_Tor_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/01:04:57_Default_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/01:04:57_Default_Tor_bridges.journal
After features/support/hooks.rb:100 0.044
Feature: Using Tor bridges and pluggable transports
Tags: @product
4:54.435
Scenario Fall back to default bridges if failing to connect directly to the Tor network
Steps
Given the Tor network is blocked 1.573
When I configure a direct connection in the Tor Connection Assistant 22.095
Then I wait until Tor is ready 4:30.766
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/tor_bridges.feature:59:in `Then I wait until Tor is ready'
And tca.conf includes no bridge 0.000
And available upgrades have been checked 0.000
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:330 5.172 
SCENARIO FAILED: 'Fall back to default bridges if failing to connect directly to the Tor network' (at time 01:10:10)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/01:10:10_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/01:10:10_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/01:10:10_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/01:10:10_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/01:10:10_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/01:10:10_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.journal
After features/support/hooks.rb:100 0.043
Feature: Using Tor bridges and pluggable transports
Tags: @product
4:59.070
Scenario Tor Connection honors my choice of using default bridges on retry, too
Steps
Given the Tor network and default bridges are blocked 2.093
When I unsuccessfully configure some default bridges in the Tor Connection Assistant 24.017
Then the Tor Connection Assistant reports that it failed to connect 0.128
Given the Tor network and default bridges are unblocked 1.458
When I click "Connect to Tor" 1.183
Then I wait until Tor is ready 4:30.189
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/tor_bridges.feature:108:in `Then I wait until Tor is ready'
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:330 5.492 
SCENARIO FAILED: 'Tor Connection honors my choice of using default bridges on retry, too' (at time 01:20:18)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/01:20:18_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/01:20:18_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/01:20:18_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/01:20:18_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/01:20:18_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/01:20:18_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.journal
After features/support/hooks.rb:100 0.038
Feature: Upgrading an old Tails USB installation
Tags: @product
1:30.367
Scenario Installing an old version of Tails to a pristine USB drive
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given a computer 0.198
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.053
And I write an old version of the Tails USB image to disk "old" 29.193
When I start Tails from USB drive "old" with network unplugged 59.879
FileNotFoundError: 
FileNotFoundError: [Errno 2] No such file or directory: '/etc/arti/arti.toml' (RemoteShell::ServerFailure)
./features/support/helpers/remote_shell.rb:71:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:42: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:234:in `open'
./features/support/helpers/remote_shell.rb:261:in `append'
./features/support/helpers/vm_helper.rb:737:in `block in file_append'
./features/support/helpers/vm_helper.rb:617:in `file_open'
./features/support/helpers/vm_helper.rb:737:in `file_append'
./features/step_definitions/chutney.rb:260:in `configure_simulated_Tor_network'
./features/step_definitions/common_steps.rb:464:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:295: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/usb_upgrade.feature:25:in `When I start Tails from USB drive "old" with network unplugged'
Then the boot device has safe access rights 0.000
And Tails is running from USB drive "old" 0.000
And there is no persistence partition on USB drive "old" 0.000
And process "udev-watchdog" is running 0.000
And udev-watchdog is monitoring the correct device 0.000
And I unplug USB drive "old" 0.000
After features/support/hooks.rb:330 4.750 
SCENARIO FAILED: 'Installing an old version of Tails to a pristine USB drive' (at time 02:23:22)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/02:23:22_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/02:23:22_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/02:23:22_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/02:23:22_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.journal
After features/support/hooks.rb:100 0.008
Feature: Upgrading an old Tails USB installation
Tags: @product
42.869
Scenario Creating a persistent partition with the old Tails USB installation
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given a computer 0.193
And I start Tails from USB drive "old" with network unplugged and I login 42.675
FileNotFoundError: 
FileNotFoundError: [Errno 2] No such file or directory: '/etc/arti/arti.toml' (RemoteShell::ServerFailure)
./features/support/helpers/remote_shell.rb:71:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:42: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:234:in `open'
./features/support/helpers/remote_shell.rb:261:in `append'
./features/support/helpers/vm_helper.rb:737:in `block in file_append'
./features/support/helpers/vm_helper.rb:617:in `file_open'
./features/support/helpers/vm_helper.rb:737:in `file_append'
./features/step_definitions/chutney.rb:260:in `configure_simulated_Tor_network'
./features/step_definitions/common_steps.rb:464:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:295: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/usb_upgrade.feature:36:in `And I start Tails from USB drive "old" with network unplugged and I login'
Then Tails is running from USB drive "old" 0.000
And I create a persistent partition 0.000
And I take note of which tps features are available 0.000
Then a Tails persistence partition exists on USB drive "old" 0.000
And I shutdown Tails and wait for the computer to power off 0.000
After features/support/hooks.rb:330 4.765 
SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 02:24:09)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/02:24:09_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/02:24:09_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/02:24:09_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/02:24:09_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.008
Feature: Upgrading an old Tails USB installation
Tags: @product
38.768
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given a computer 0.197
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 38.571
FileNotFoundError: 
FileNotFoundError: [Errno 2] No such file or directory: '/etc/arti/arti.toml' (RemoteShell::ServerFailure)
./features/support/helpers/remote_shell.rb:71:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:42: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:234:in `open'
./features/support/helpers/remote_shell.rb:261:in `append'
./features/support/helpers/vm_helper.rb:737:in `block in file_append'
./features/support/helpers/vm_helper.rb:617:in `file_open'
./features/support/helpers/vm_helper.rb:737:in `file_append'
./features/step_definitions/chutney.rb:260:in `configure_simulated_Tor_network'
./features/step_definitions/common_steps.rb:464:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:295: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/usb_upgrade.feature:46:in `And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled'
Then Tails is running from USB drive "old" 0.000
And all tps features are active 0.000
When I write some files expected to persist 0.000
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.000
And all persistence configuration files have safe access rights 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
And I take note of which tps features are available 0.000
And I shutdown Tails and wait for the computer to power off 0.000
# XXX: how does guestfs work vs snapshots?
Then only the expected files are present on the persistence partition on USB drive "old" 0.000
After features/support/hooks.rb:330 4.820 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 02:24:53)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/02:24:53_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/02:24:53_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/02:24:53_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/02:24:53_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.007
Feature: Upgrading an old Tails USB installation
Tags: @product
1:19.588
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given a computer 0.204
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:19.383
The 
The Dogtail init script raised: SearchError: descendent 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:671:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:703:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:302: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/usb_upgrade.feature:73:in `And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled'
Then all tps features from the old Tails version are active 0.000
And Tails is running from USB drive "to_upgrade" 0.000
And the boot device has safe access rights 0.000
And the expected persistent files created with the old Tails version are present in the filesystem 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
After features/support/hooks.rb:330 5.011 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:28:59)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/02:28:59_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/02:28:59_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/02:28:59_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/02:28:59_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.011
Feature: Using persistent Tor bridges and pluggable transports
5:32.726
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 11.339
And I create a persistent partition with the default settings 24.670
Then the "TorConfiguration" tps feature is not enabled 2.932
When the network is plugged 0.070
And the Tor Connection Assistant autostarts 11.644
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 11.431
And I wait until Tor is ready 4:30.639
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/persistent_tor_bridges.feature:14:in `And I wait until Tor is ready'
Then tca.conf includes the configured bridges 0.000
And the "TorConfiguration" tps feature is enabled and active 0.000
When I cold reboot the computer 0.000
And the computer reboots Tails 0.000
And I enable persistence 0.000
And I capture all network traffic 0.000
And I log in to a new session 0.000
Then tca.conf includes the configured bridges 0.000
When the network is plugged 0.000
And the Tor Connection Assistant autostarts 0.000
Feature: Using persistent Tor bridges and pluggable transports
Tags: @product
0.000
Scenario Using Persistent Tor bridges
Steps
When I choose to connect to Tor automatically 0.000
And I accept Tor Connection's offer to use my persistent bridges 0.000
And I click "Connect to Tor" 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes the configured bridges 0.000
And the "TorConfiguration" tps feature is enabled and active 0.000
And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.000
After features/support/hooks.rb:330 6.110 
SCENARIO FAILED: 'Using Persistent Tor bridges' (at time 04:45:23)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/04:45:23_Using_Persistent_Tor_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/04:45:23_Using_Persistent_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/04:45:23_Using_Persistent_Tor_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/04:45:23_Using_Persistent_Tor_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/04:45:23_Using_Persistent_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/04:45:23_Using_Persistent_Tor_bridges.journal
After features/support/hooks.rb:100 0.000
Feature: Using persistent Tor bridges and pluggable transports
5:23.528
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 9.829
And I create a persistent partition with the default settings 20.623
Then the "TorConfiguration" tps feature is not enabled 2.817
When the network is plugged 0.072
And the Tor Connection Assistant autostarts 8.205
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 11.443
And I wait until Tor is ready 4:30.534
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
features/persistent_tor_bridges.feature:14:in `And I wait until Tor is ready'
Then tca.conf includes the configured bridges 0.000
And the "TorConfiguration" tps feature is enabled and active 0.000
When I cold reboot the computer 0.000
And the computer reboots Tails 0.000
And I enable persistence 0.000
And I capture all network traffic 0.000
And I log in to a new session 0.000
Then tca.conf includes the configured bridges 0.000
When the network is plugged 0.000
And the Tor Connection Assistant autostarts 0.000
Feature: Using persistent Tor bridges and pluggable transports
Tags: @product
0.000
Scenario Disabling persistence of Tor bridges
Steps
When I choose to connect to Tor automatically 0.000
And I accept Tor Connection's offer to use my persistent bridges 0.000
And I disable saving bridges to Persistent Storage 0.000
And I configure a direct connection in the Tor Connection Assistant 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes no bridge 0.000
And the "TorConfiguration" tps feature is not enabled and not active 0.000
And all Internet traffic has only flowed through Tor or connectivity check service 0.000
After features/support/hooks.rb:330 5.416 
SCENARIO FAILED: 'Disabling persistence of Tor bridges' (at time 04:50:53)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/04:50:53_Disabling_persistence_of_Tor_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/04:50:53_Disabling_persistence_of_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/04:50:53_Disabling_persistence_of_Tor_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/04:50:53_Disabling_persistence_of_Tor_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/04:50:53_Disabling_persistence_of_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/04:50:53_Disabling_persistence_of_Tor_bridges.journal
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
1:54.667
Scenario The Tor Browser cannot access the LAN
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD and logged in and the network is connected 12.913
And a web server is running on the LAN 1.052
And I capture all network traffic 0.005
When I start the Tor Browser 28.816
And the Tor Browser loads the startup page 1.066
And I open a page on the LAN web server in the Tor Browser 10.811
Then the Tor Browser shows the "Unable to connect" error 1:0.000
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: descendent of [application | Firefox]: child with name="Problem loading page" roleName='document web'
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/browser.rb:320:in `headings_in_page'
./features/step_definitions/browser.rb:324:in `page_has_heading'
./features/step_definitions/browser.rb:335:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/browser.rb:334:in `block in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/browser.rb:334:in `/^the (Tor|Unsafe) Browser shows the "([^"]+)" error$/'
features/torified_browsing.feature:14:in `Then the Tor Browser shows the "Unable to connect" error'
And no traffic was sent to the web server on the LAN 0.000
After features/support/hooks.rb:330 6.891 
SCENARIO FAILED: 'The Tor Browser cannot access the LAN' (at time 05:12:18)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/05:12:18_The_Tor_Browser_cannot_access_the_LAN.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/05:12:18_The_Tor_Browser_cannot_access_the_LAN.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/05:12:18_The_Tor_Browser_cannot_access_the_LAN.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/05:12:18_The_Tor_Browser_cannot_access_the_LAN.journal
After features/support/hooks.rb:100 0.054
Feature: Browsing the web using the Tor Browser
Tags: @product
1:10.627
Scenario The Tor Browser's circuit view feature works as expected
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given I have started Tails from DVD and logged in and the network is connected 11.296
When I start the Tor Browser 27.717
And the Tor Browser loads the startup page 1.095
Then Tor Browser's circuit view is working 30.518
The 
The Dogtail init script raised: SearchError: descendent of [application | Firefox]: child with name="Tor Circuit" roleName='push button'
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:435:in `/^Tor Browser's circuit view is working$/'
features/torified_browsing.feature:93:in `Then Tor Browser's circuit view is working'
After features/support/hooks.rb:330 5.793 
SCENARIO FAILED: 'The Tor Browser's circuit view feature works as expected' (at time 05:21:42)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/05:21:42_The_Tor_Browser_s_circuit_view_feature_works_as_expected.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/05:21:42_The_Tor_Browser_s_circuit_view_feature_works_as_expected.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/05:21:42_The_Tor_Browser_s_circuit_view_feature_works_as_expected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/52/artifact/build-artifacts/05:21:42_The_Tor_Browser_s_circuit_view_feature_works_as_expected.journal
After features/support/hooks.rb:100 0.000