Project Number Date
test_Tails_ISO_19139-arti-bridges 5 18 Nov 2024, 21:53

Failures Overview

The following summary displays scenarios that failed.

Feature: Time syncing
Tags: @product @check_tor_leaks
4:54.655
Scenario Clock with host's time while using bridges
Before features/support/hooks.rb:269 0.002
Before features/support/hooks.rb:503 0.002
Steps
Given I have started Tails from DVD without network and logged in 7.780
When the network is plugged 0.077
And the Tor Connection Assistant autostarts 3.862
And I configure some normal bridges in the Tor Connection Assistant 12.304
And I wait until Tor is ready 4:30.630
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:703:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:665: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:511 0.033
After features/support/hooks.rb:326 5.112 
SCENARIO FAILED: 'Clock with host's time while using bridges' (at time 00:15:57)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/00:15:57_Clock_with_host_s_time_while_using_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/00:15:57_Clock_with_host_s_time_while_using_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/00:15:57_Clock_with_host_s_time_while_using_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/00:15:57_Clock_with_host_s_time_while_using_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/00:15:57_Clock_with_host_s_time_while_using_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/00:15:57_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.857
Scenario Clock is one day in the future while using obfs4 bridges
Before features/support/hooks.rb:269 0.002
Before features/support/hooks.rb:503 0.005
Steps
Given I have started Tails from DVD without network and logged in 7.789
When I bump the system time with "+1 day" 0.237
And I capture all network traffic 0.002
And the network is plugged 0.107
And the Tor Connection Assistant autostarts 3.900
And I configure some obfs4 bridges in the Tor Connection Assistant in easy mode 13.903
And I wait until Tor is ready 4:30.915
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:703:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:665: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:511 0.029
After features/support/hooks.rb:326 5.051 
SCENARIO FAILED: 'Clock is one day in the future while using obfs4 bridges' (at time 00:20:59)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/00:20:59_Clock_is_one_day_in_the_future_while_using_obfs4_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/00:20:59_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_19139-arti-bridges/5/artifact/build-artifacts/00:20:59_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/00:20:59_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/00:20:59_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/00:20:59_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.journal
After features/support/hooks.rb:100 0.051
Feature: Time syncing
Tags: @product @check_tor_leaks
5:24.941
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:269 0.002
Before features/support/hooks.rb:503 0.002
Steps
Given I have started Tails from DVD without network and logged in 7.802
When I bump the system time with "+8 hours +15 minutes" 0.199
And all notifications have disappeared 3.983
And I capture all network traffic 0.002
And I make sure time sync before Tor connects fails 0.093
And the network is plugged 0.066
And the Tor Connection Assistant autostarts 3.415
When I configure the default bridges in the Tor Connection Assistant in easy mode without connecting 5.030
And I click "Connect to Tor" 1.145
And the Tor Connection Assistant fails to connect to Tor 16.717
# The "Fix Clock" button allows users to recover from this bug
Then I set the time zone in Tor Connection to "Asia/Shanghai" 14.933
Then the system clock is less than 20 minutes incorrect 0.222
When I click "Connect to Tor" 1.153
Then I wait until Tor is ready 4:30.173
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:703:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:665: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:511 0.034
After features/support/hooks.rb:326 5.535 
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:30:35)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/00:30:35_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_19139-arti-bridges/5/artifact/build-artifacts/00:30:35_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_19139-arti-bridges/5/artifact/build-artifacts/00:30:35_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_19139-arti-bridges/5/artifact/build-artifacts/00:30:35_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_19139-arti-bridges/5/artifact/build-artifacts/00:30:35_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_19139-arti-bridges/5/artifact/build-artifacts/00:30:35_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.035
Feature: Time syncing
Tags: @product @check_tor_leaks
5:19.098
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:269 0.002
Before features/support/hooks.rb:503 0.003
Steps
Given I have started Tails from DVD without network and logged in 7.729
When I bump the system time with "+8 hours +15 minutes" 0.173
And all notifications have disappeared 4.132
And I capture all network traffic 0.003
And the network is plugged 0.060
And the Tor Connection Assistant autostarts 2.794
# 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.573
And I click "Connect to Tor" 1.179
Then the Tor Connection Assistant reports that it failed to connect 11.793
# The "Fix Clock" button allows users to recover from this bug
When I set the time zone in Tor Connection to "Asia/Shanghai" 14.667
Then the system clock is less than 20 minutes incorrect 0.319
# "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.358
When I click "Connect to Tor" 1.149
Then I wait until Tor is ready 4:30.162
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:703:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:665: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:511 0.029
After features/support/hooks.rb:326 5.131 
SCENARIO FAILED: 'I can connect to obfs4 bridges having a clock East of UTC while hiding that I am using Tor' (at time 00:36:00)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/00:36:00_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_19139-arti-bridges/5/artifact/build-artifacts/00:36:00_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_19139-arti-bridges/5/artifact/build-artifacts/00:36:00_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_19139-arti-bridges/5/artifact/build-artifacts/00:36:00_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_19139-arti-bridges/5/artifact/build-artifacts/00:36:00_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_19139-arti-bridges/5/artifact/build-artifacts/00:36:00_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.035
Feature: Using Tor bridges and pluggable transports
Tags: @product
4:43.137
Scenario Using normal bridges
Steps
When I configure some normal bridges in the Tor Connection Assistant 12.325
Then I wait until Tor is ready 4:30.811
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:703:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:665: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:326 5.137 
SCENARIO FAILED: 'Using normal bridges' (at time 00:41:22)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/00:41:22_Using_normal_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/00:41:22_Using_normal_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/00:41:22_Using_normal_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/00:41:22_Using_normal_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/00:41:22_Using_normal_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/00:41:22_Using_normal_bridges.journal
After features/support/hooks.rb:100 0.031
Feature: Using Tor bridges and pluggable transports
Tags: @product
4:41.648
Scenario Using obfs4 pluggable transports
Steps
When I configure some obfs4 bridges in the Tor Connection Assistant in hide mode 10.805
Then I wait until Tor is ready 4:30.842
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:703:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:665: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:326 5.165 
SCENARIO FAILED: 'Using obfs4 pluggable transports' (at time 00:46:21)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/00:46:21_Using_obfs4_pluggable_transports_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/00:46:21_Using_obfs4_pluggable_transports.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/00:46:21_Using_obfs4_pluggable_transports.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/00:46:21_Using_obfs4_pluggable_transports.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/00:46:21_Using_obfs4_pluggable_transports.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/00:46:21_Using_obfs4_pluggable_transports.journal
After features/support/hooks.rb:100 0.030
Feature: Using Tor bridges and pluggable transports
Tags: @product
5:4.120
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 33.233
Then I wait until Tor is ready 4:30.886
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:703:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:665: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:326 5.356 
SCENARIO FAILED: 'Using obfs4 pluggable transports from a QR code' (at time 00:51:42)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/00:51:42_Using_obfs4_pluggable_transports_from_a_QR_code_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/00:51:42_Using_obfs4_pluggable_transports_from_a_QR_code.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/00:51:42_Using_obfs4_pluggable_transports_from_a_QR_code.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/00:51:42_Using_obfs4_pluggable_transports_from_a_QR_code.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/00:51:42_Using_obfs4_pluggable_transports_from_a_QR_code.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/00:51:42_Using_obfs4_pluggable_transports_from_a_QR_code.journal
After features/support/hooks.rb:100 0.043
Feature: Using Tor bridges and pluggable transports
Tags: @product
5:27.756
Scenario TCA can scan QR code after a connection failure
Steps
Given the Tor network and default bridges are blocked 1.668
When I unsuccessfully configure a direct connection in the Tor Connection Assistant 31.742
Then the Tor Connection Assistant reports that it failed to connect 0.116
And tca.conf is empty 0.299
Given I scan a QR code from the error page in Tor Connection Assistant 22.124
And I retry connecting to Tor 1.140
Then I wait until Tor is ready 4:30.664
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:703:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:665: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:326 5.214 
SCENARIO FAILED: 'TCA can scan QR code after a connection failure' (at time 00:57:27)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/00:57:27_TCA_can_scan_QR_code_after_a_connection_failure_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/00:57:27_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_19139-arti-bridges/5/artifact/build-artifacts/00:57:27_TCA_can_scan_QR_code_after_a_connection_failure.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/00:57:27_TCA_can_scan_QR_code_after_a_connection_failure.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/00:57:27_TCA_can_scan_QR_code_after_a_connection_failure.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/00:57:27_TCA_can_scan_QR_code_after_a_connection_failure.journal
After features/support/hooks.rb:100 0.046
Feature: Using Tor bridges and pluggable transports
Tags: @product @supports_real_tor
4:44.495
Scenario Default Tor bridges
Steps
When I configure the default bridges in the Tor Connection Assistant 13.423
Then I wait until Tor is ready 4:31.071
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:703:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:665: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:326 5.175 
SCENARIO FAILED: 'Default Tor bridges' (at time 01:02:29)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/01:02:29_Default_Tor_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/01:02:29_Default_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/01:02:29_Default_Tor_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/01:02:29_Default_Tor_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/01:02:29_Default_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/01:02:29_Default_Tor_bridges.journal
After features/support/hooks.rb:100 0.045
Feature: Using Tor bridges and pluggable transports
Tags: @product
4:53.614
Scenario Fall back to default bridges if failing to connect directly to the Tor network
Steps
Given the Tor network is blocked 1.620
When I configure a direct connection in the Tor Connection Assistant 21.477
Then I wait until Tor is ready 4:30.516
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:703:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:665: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:326 5.174 
SCENARIO FAILED: 'Fall back to default bridges if failing to connect directly to the Tor network' (at time 01:07:39)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/01:07:39_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_19139-arti-bridges/5/artifact/build-artifacts/01:07:39_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_19139-arti-bridges/5/artifact/build-artifacts/01:07:39_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_19139-arti-bridges/5/artifact/build-artifacts/01:07:39_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_19139-arti-bridges/5/artifact/build-artifacts/01:07:39_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_19139-arti-bridges/5/artifact/build-artifacts/01:07:39_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.journal
After features/support/hooks.rb:100 0.036
Feature: Using Tor bridges and pluggable transports
Tags: @product
4:57.267
Scenario Tor Connection honors my choice of using default bridges on retry, too
Steps
Given the Tor network and default bridges are blocked 1.785
When I unsuccessfully configure some default bridges in the Tor Connection Assistant 22.715
Then the Tor Connection Assistant reports that it failed to connect 0.119
Given the Tor network and default bridges are unblocked 1.344
When I click "Connect to Tor" 1.143
Then I wait until Tor is ready 4:30.157
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:703:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:665: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:326 5.272 
SCENARIO FAILED: 'Tor Connection honors my choice of using default bridges on retry, too' (at time 01:17:38)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/01:17:38_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_19139-arti-bridges/5/artifact/build-artifacts/01:17:38_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_19139-arti-bridges/5/artifact/build-artifacts/01:17:38_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/01:17:38_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/01:17:38_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/01:17:38_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.journal
After features/support/hooks.rb:100 0.056
Feature: Upgrading an old Tails USB installation
Tags: @product
2:0.484
Scenario Installing an old version of Tails to a pristine USB drive
Before features/support/hooks.rb:269 0.005
Steps
Given a computer 0.160
And I create a 7200 MiB disk named "old" 0.042
And I plug USB drive "old" 1.048
And I write an old version of the Tails USB image to disk "old" 30.262
When I start Tails from USB drive "old" with network unplugged 1:28.970
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:711:in `block in file_append'
./features/support/helpers/vm_helper.rb:604:in `file_open'
./features/support/helpers/vm_helper.rb:711:in `file_append'
./features/step_definitions/chutney.rb:260:in `configure_simulated_Tor_network'
./features/step_definitions/common_steps.rb:467: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:326 4.775 
SCENARIO FAILED: 'Installing an old version of Tails to a pristine USB drive' (at time 02:19:50)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/02:19:50_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_19139-arti-bridges/5/artifact/build-artifacts/02:19:50_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/02:19:50_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/02:19:50_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.journal
After features/support/hooks.rb:100 0.009
Feature: Upgrading an old Tails USB installation
Tags: @product
58.946
Scenario Creating a persistent partition with the old Tails USB installation
Before features/support/hooks.rb:269 0.005
Steps
Given a computer 0.167
And I start Tails from USB drive "old" with network unplugged and I login 58.778
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:711:in `block in file_append'
./features/support/helpers/vm_helper.rb:604:in `file_open'
./features/support/helpers/vm_helper.rb:711:in `file_append'
./features/step_definitions/chutney.rb:260:in `configure_simulated_Tor_network'
./features/step_definitions/common_steps.rb:467: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:326 4.855 
SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 02:20:53)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/02:20:53_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_19139-arti-bridges/5/artifact/build-artifacts/02:20:53_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/02:20:53_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/02:20:53_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
57.739
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:269 0.005
Steps
Given a computer 0.157
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 57.582
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:711:in `block in file_append'
./features/support/helpers/vm_helper.rb:604:in `file_open'
./features/support/helpers/vm_helper.rb:711:in `file_append'
./features/step_definitions/chutney.rb:260:in `configure_simulated_Tor_network'
./features/step_definitions/common_steps.rb:467: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:326 4.826 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 02:21:56)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/02:21:56_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_19139-arti-bridges/5/artifact/build-artifacts/02:21:56_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_19139-arti-bridges/5/artifact/build-artifacts/02:21:56_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_19139-arti-bridges/5/artifact/build-artifacts/02:21:56_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.009
Feature: Upgrading an old Tails USB installation
Tags: @product
1:12.175
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:269 0.005
Steps
Given a computer 0.168
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:12.006
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:668:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:700: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:326 4.996 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:25:53)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/02:25:53_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_19139-arti-bridges/5/artifact/build-artifacts/02:25:53_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/02:25:53_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/02:25:53_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.008
Feature: Networking
Tags: @product @not_release_blocker
3:14.773
Scenario The Tails Greeter "disable all networking" option disables networking within Tails
Before features/support/hooks.rb:269 0.006
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 7.859
And I disable networking in Tails Greeter 2.002
And I log in to a new session 3:4.911
cannot 
cannot find GnomeApplicationsMenu.png on the screen (FindFailed)
./features/support/helpers/screen.rb:173:in `rescue in wait'
./features/support/helpers/screen.rb:157:in `wait'
./features/step_definitions/common_steps.rb:570:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:526:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
features/networking.feature:18:in `And I log in to a new session'
Then no network interfaces are enabled 0.000
When I hotplug a network device 0.000
And I wait 10 seconds 0.000
Then no network interfaces are enabled 0.000
After features/support/hooks.rb:326 5.062 
SCENARIO FAILED: 'The Tails Greeter "disable all networking" option disables networking within Tails' (at time 03:34:38)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/03:34:38_The_Tails_Greeter__disable_all_networking__option_disables_networking_within_Tails.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/03:34:38_The_Tails_Greeter__disable_all_networking__option_disables_networking_within_Tails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/03:34:38_The_Tails_Greeter__disable_all_networking__option_disables_networking_within_Tails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/03:34:38_The_Tails_Greeter__disable_all_networking__option_disables_networking_within_Tails.journal
After features/support/hooks.rb:100 0.000
Feature: Using persistent Tor bridges and pluggable transports
5:24.809
Background
Before features/support/hooks.rb:269 0.006
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 10.814
And I create a persistent partition with the default settings 20.988
Then the "TorConfiguration" tps feature is not enabled 1.221
When the network is plugged 0.062
And the Tor Connection Assistant autostarts 9.690
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 11.578
And I wait until Tor is ready 4:30.454
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:703:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:665: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:326 5.438 
SCENARIO FAILED: 'Using Persistent Tor bridges' (at time 04:17:58)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/04:17:58_Using_Persistent_Tor_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/04:17:58_Using_Persistent_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/04:17:58_Using_Persistent_Tor_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/04:17:58_Using_Persistent_Tor_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/04:17:58_Using_Persistent_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/04:17:58_Using_Persistent_Tor_bridges.journal
After features/support/hooks.rb:100 0.000
Feature: Using persistent Tor bridges and pluggable transports
5:18.802
Background
Before features/support/hooks.rb:269 0.006
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 9.312
And I create a persistent partition with the default settings 19.748
Then the "TorConfiguration" tps feature is not enabled 1.082
When the network is plugged 0.060
And the Tor Connection Assistant autostarts 6.790
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 11.403
And I wait until Tor is ready 4:30.404
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:703:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:665: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:326 5.481 
SCENARIO FAILED: 'Disabling persistence of Tor bridges' (at time 04:23:22)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/04:23:22_Disabling_persistence_of_Tor_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/04:23:22_Disabling_persistence_of_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/04:23:22_Disabling_persistence_of_Tor_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/04:23:22_Disabling_persistence_of_Tor_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/04:23:22_Disabling_persistence_of_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/04:23:22_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:50.338
Scenario The Tor Browser cannot access the LAN
Before features/support/hooks.rb:269 0.006
Steps
Given I have started Tails from DVD and logged in and the network is connected 11.374
And a web server is running on the LAN 1.034
And I capture all network traffic 0.006
When I start the Tor Browser 24.742
And the Tor Browser loads the startup page 0.901
And I open a page on the LAN web server in the Tor Browser 12.273
Then the Tor Browser shows the "Unable to connect" error 1:0.004
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:317:in `headings_in_page'
./features/step_definitions/browser.rb:321:in `page_has_heading'
./features/step_definitions/browser.rb:332: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:331: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:331: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:326 10.592 
SCENARIO FAILED: 'The Tor Browser cannot access the LAN' (at time 04:42:56)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/04:42:56_The_Tor_Browser_cannot_access_the_LAN.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/04:42:56_The_Tor_Browser_cannot_access_the_LAN.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/04:42:56_The_Tor_Browser_cannot_access_the_LAN.journal
After features/support/hooks.rb:100 0.038
Feature: Browsing the web using the Tor Browser
Tags: @product
1:3.719
Scenario The Tor Browser's circuit view feature works as expected
Before features/support/hooks.rb:269 0.007
Steps
Given I have started Tails from DVD and logged in and the network is connected 12.269
When I start the Tor Browser 25.230
And the Tor Browser loads the startup page 0.942
Then Tor Browser's circuit view is working 25.277
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:432:in `/^Tor Browser's circuit view is working$/'
features/torified_browsing.feature:107:in `Then Tor Browser's circuit view is working'
After features/support/hooks.rb:326 5.288 
SCENARIO FAILED: 'The Tor Browser's circuit view feature works as expected' (at time 04:51:31)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/04:51:31_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_19139-arti-bridges/5/artifact/build-artifacts/04:51:31_The_Tor_Browser_s_circuit_view_feature_works_as_expected.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/04:51:31_The_Tor_Browser_s_circuit_view_feature_works_as_expected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/5/artifact/build-artifacts/04:51:31_The_Tor_Browser_s_circuit_view_feature_works_as_expected.journal
After features/support/hooks.rb:100 0.000