Project Number Date
test_Tails_ISO_feature-arti 5 20 Nov 2024, 16:40

Failures Overview

The following summary displays scenarios that failed.

Feature: Time syncing
Tags: @product @check_tor_leaks
4:57.222
Scenario Clock with host's time while using bridges
Before features/support/hooks.rb:269 0.003
Before features/support/hooks.rb:503 0.002
Steps
Given I have started Tails from DVD without network and logged in 8.762
When the network is plugged 0.100
And the Tor Connection Assistant autostarts 4.061
And I configure some normal bridges in the Tor Connection Assistant 13.478
And I wait until Tor is ready 4:30.820
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.028
After features/support/hooks.rb:326 5.256 
SCENARIO FAILED: 'Clock with host's time while using bridges' (at time 00:16:50)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/00:16:50_Clock_with_host_s_time_while_using_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/00:16:50_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/5/artifact/build-artifacts/00:16:50_Clock_with_host_s_time_while_using_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/00:16:50_Clock_with_host_s_time_while_using_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/00:16:50_Clock_with_host_s_time_while_using_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/00:16:50_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:58.144
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.002
Steps
Given I have started Tails from DVD without network and logged in 8.526
When I bump the system time with "+1 day" 0.195
And I capture all network traffic 0.002
And the network is plugged 0.083
And the Tor Connection Assistant autostarts 3.431
And I configure some obfs4 bridges in the Tor Connection Assistant in easy mode 15.244
And I wait until Tor is ready 4:30.660
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.039
After features/support/hooks.rb:326 5.312 
SCENARIO FAILED: 'Clock is one day in the future while using obfs4 bridges' (at time 00:21:53)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/00:21:53_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/5/artifact/build-artifacts/00:21:53_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/5/artifact/build-artifacts/00:21:53_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/5/artifact/build-artifacts/00:21:53_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/00:21:53_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/5/artifact/build-artifacts/00:21:53_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.journal
After features/support/hooks.rb:100 0.054
Feature: Time syncing
Tags: @product @check_tor_leaks
5:27.543
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.003
Before features/support/hooks.rb:503 0.003
Steps
Given I have started Tails from DVD without network and logged in 8.785
When I bump the system time with "+8 hours +15 minutes" 0.249
And all notifications have disappeared 4.013
And I capture all network traffic 0.002
And I make sure time sync before Tor connects fails 0.137
And the network is plugged 0.089
And the Tor Connection Assistant autostarts 4.830
When I configure the default bridges in the Tor Connection Assistant in easy mode without connecting 5.324
And I click "Connect to Tor" 1.192
And the Tor Connection Assistant fails to connect to Tor 16.440
# The "Fix Clock" button allows users to recover from this bug
Then I set the time zone in Tor Connection to "Asia/Shanghai" 14.911
Then the system clock is less than 20 minutes incorrect 0.203
When I click "Connect to Tor" 1.166
Then I wait until Tor is ready 4:30.195
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.370 
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:44)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/00:32:44_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/5/artifact/build-artifacts/00:32:44_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/5/artifact/build-artifacts/00:32:44_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/5/artifact/build-artifacts/00:32:44_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/5/artifact/build-artifacts/00:32:44_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/5/artifact/build-artifacts/00:32:44_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.059
Feature: Time syncing
Tags: @product @check_tor_leaks
5:21.102
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.003
Before features/support/hooks.rb:503 0.002
Steps
Given I have started Tails from DVD without network and logged in 8.283
When I bump the system time with "+8 hours +15 minutes" 0.263
And all notifications have disappeared 4.124
And I capture all network traffic 0.002
And the network is plugged 0.096
And the Tor Connection Assistant autostarts 3.429
# 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.824
And I click "Connect to Tor" 1.182
Then the Tor Connection Assistant reports that it failed to connect 12.064
# The "Fix Clock" button allows users to recover from this bug
When I set the time zone in Tor Connection to "Asia/Shanghai" 14.954
Then the system clock is less than 20 minutes incorrect 0.234
# "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.381
When I click "Connect to Tor" 1.163
Then I wait until Tor is ready 4:30.097
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.040
After features/support/hooks.rb:326 5.138 
SCENARIO FAILED: 'I can connect to obfs4 bridges having a clock East of UTC while hiding that I am using Tor' (at time 00:38:11)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/00:38:11_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/5/artifact/build-artifacts/00:38:11_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/5/artifact/build-artifacts/00:38:11_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/5/artifact/build-artifacts/00:38:11_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/5/artifact/build-artifacts/00:38:11_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/5/artifact/build-artifacts/00:38:11_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.032
Feature: Using Tor bridges and pluggable transports
Tags: @product
4:44.283
Scenario Using normal bridges
Steps
When I configure some normal bridges in the Tor Connection Assistant 13.460
Then I wait until Tor is ready 4:30.823
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.251 
SCENARIO FAILED: 'Using normal bridges' (at time 00:43:40)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/00:43:40_Using_normal_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/00:43:40_Using_normal_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/00:43:40_Using_normal_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/00:43:40_Using_normal_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/00:43:40_Using_normal_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/00:43:40_Using_normal_bridges.journal
After features/support/hooks.rb:100 0.049
Feature: Using Tor bridges and pluggable transports
Tags: @product
4:42.668
Scenario Using obfs4 pluggable transports
Steps
When I configure some obfs4 bridges in the Tor Connection Assistant in hide mode 11.923
Then I wait until Tor is ready 4:30.745
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.299 
SCENARIO FAILED: 'Using obfs4 pluggable transports' (at time 00:48:41)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/00:48:41_Using_obfs4_pluggable_transports_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/00:48:41_Using_obfs4_pluggable_transports.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/00:48:41_Using_obfs4_pluggable_transports.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/00:48:41_Using_obfs4_pluggable_transports.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/00:48:41_Using_obfs4_pluggable_transports.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/00:48:41_Using_obfs4_pluggable_transports.journal
After features/support/hooks.rb:100 0.045
Feature: Using Tor bridges and pluggable transports
Tags: @product
5:3.849
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.159
Then I wait until Tor is ready 4:30.690
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.581 
SCENARIO FAILED: 'Using obfs4 pluggable transports from a QR code' (at time 00:54:04)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/00:54:04_Using_obfs4_pluggable_transports_from_a_QR_code_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/00:54:04_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/5/artifact/build-artifacts/00:54:04_Using_obfs4_pluggable_transports_from_a_QR_code.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/00:54:04_Using_obfs4_pluggable_transports_from_a_QR_code.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/00:54:04_Using_obfs4_pluggable_transports_from_a_QR_code.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/00:54:04_Using_obfs4_pluggable_transports_from_a_QR_code.journal
After features/support/hooks.rb:100 0.041
Feature: Using Tor bridges and pluggable transports
Tags: @product
5:28.330
Scenario TCA can scan QR code after a connection failure
Steps
Given the Tor network and default bridges are blocked 2.192
When I unsuccessfully configure a direct connection in the Tor Connection Assistant 31.988
Then the Tor Connection Assistant reports that it failed to connect 0.126
And tca.conf is empty 0.225
Given I scan a QR code from the error page in Tor Connection Assistant 22.017
And I retry connecting to Tor 1.180
Then I wait until Tor is ready 4:30.599
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.319 
SCENARIO FAILED: 'TCA can scan QR code after a connection failure' (at time 00:59:51)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/00:59:51_TCA_can_scan_QR_code_after_a_connection_failure_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/00:59:51_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/5/artifact/build-artifacts/00:59:51_TCA_can_scan_QR_code_after_a_connection_failure.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/00:59:51_TCA_can_scan_QR_code_after_a_connection_failure.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/00:59:51_TCA_can_scan_QR_code_after_a_connection_failure.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/00:59:51_TCA_can_scan_QR_code_after_a_connection_failure.journal
After features/support/hooks.rb:100 0.053
Feature: Using Tor bridges and pluggable transports
Tags: @product @supports_real_tor
4:45.005
Scenario Default Tor bridges
Steps
When I configure the default bridges in the Tor Connection Assistant 14.185
Then I wait until Tor is ready 4:30.819
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.301 
SCENARIO FAILED: 'Default Tor bridges' (at time 01:04:56)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/01:04:56_Default_Tor_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/01:04:56_Default_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/01:04:56_Default_Tor_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/01:04:56_Default_Tor_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/01:04:56_Default_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/01:04:56_Default_Tor_bridges.journal
After features/support/hooks.rb:100 0.054
Feature: Using Tor bridges and pluggable transports
Tags: @product
4:53.195
Scenario Fall back to default bridges if failing to connect directly to the Tor network
Steps
Given the Tor network is blocked 1.877
When I configure a direct connection in the Tor Connection Assistant 20.765
Then I wait until Tor is ready 4:30.552
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.353 
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/5/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/5/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/5/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/5/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/5/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/5/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.039
Feature: Using Tor bridges and pluggable transports
Tags: @product
4:59.884
Scenario Tor Connection honors my choice of using default bridges on retry, too
Steps
Given the Tor network and default bridges are blocked 2.864
When I unsuccessfully configure some default bridges in the Tor Connection Assistant 24.025
Then the Tor Connection Assistant reports that it failed to connect 0.136
Given the Tor network and default bridges are unblocked 1.546
When I click "Connect to Tor" 1.160
Then I wait until Tor is ready 4:30.150
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.396 
SCENARIO FAILED: 'Tor Connection honors my choice of using default bridges on retry, too' (at time 01:21:21)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/01:21:21_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/5/artifact/build-artifacts/01:21:21_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/5/artifact/build-artifacts/01:21:21_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/5/artifact/build-artifacts/01:21:21_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/5/artifact/build-artifacts/01:21:21_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/5/artifact/build-artifacts/01:21:21_Tor_Connection_honors_my_choice_of_using_default_bridges_on_retry,_too.journal
After features/support/hooks.rb:100 0.034
Feature: Upgrading an old Tails USB installation
Tags: @product
2:4.643
Scenario Installing an old version of Tails to a pristine USB drive
Before features/support/hooks.rb:269 0.004
Steps
Given a computer 0.219
And I create a 7200 MiB disk named "old" 0.052
And I plug USB drive "old" 1.085
And I write an old version of the Tails USB image to disk "old" 30.035
When I start Tails from USB drive "old" with network unplugged 1:33.250
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.864 
SCENARIO FAILED: 'Installing an old version of Tails to a pristine USB drive' (at time 02:25:14)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/02:25:14_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/5/artifact/build-artifacts/02:25:14_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/02:25:14_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/5/artifact/build-artifacts/02:25:14_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
1:0.695
Scenario Creating a persistent partition with the old Tails USB installation
Before features/support/hooks.rb:269 0.005
Steps
Given a computer 0.195
And I start Tails from USB drive "old" with network unplugged and I login 1:0.499
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.877 
SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 02:26:19)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/02:26:19_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/5/artifact/build-artifacts/02:26:19_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/02:26:19_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/02:26:19_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:100 0.010
Feature: Upgrading an old Tails USB installation
Tags: @product
59.553
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.194
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.359
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.871 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 02:27:24)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/02:27:24_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/5/artifact/build-artifacts/02:27:24_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/5/artifact/build-artifacts/02:27:24_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/5/artifact/build-artifacts/02:27:24_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:14.990
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:269 0.006
Steps
Given a computer 0.185
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:14.805
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 5.090 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:31:19)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/02:31:19_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/5/artifact/build-artifacts/02:31:19_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/5/artifact/build-artifacts/02:31:19_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/5/artifact/build-artifacts/02:31:19_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.010
Feature: Tails persistence
Tags: @product
22:37.077
Scenario Booting Tails from a USB drive with an enabled persistent partition and reconfiguring it
Before features/support/hooks.rb:269 0.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.708
Then Tails is running from USB drive "__internal" 0.590
And all tps features are active 2.448
And all persistent directories have safe access rights 2.611
When I disable the first tps feature 5.748
Then all tps features but the first one are active 2.183
And I shutdown Tails and wait for the computer to power off 13.404
And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 21:58.382
execution 
execution expired (RemoteShell::Timeout)
./features/support/helpers/remote_shell.rb:56:in `read'
./features/support/helpers/remote_shell.rb:56:in `block (3 levels) in communicate'
./features/support/helpers/remote_shell.rb:55:in `block (2 levels) in communicate'
./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:174:in `execute'
./features/support/helpers/remote_shell.rb:185:in `initialize'
./features/support/helpers/dogtail.rb:80:in `new'
./features/support/helpers/dogtail.rb:80:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:723:in `new'
./features/step_definitions/common_steps.rb:723:in `/^all notifications have disappeared$/'
./features/step_definitions/common_steps.rb:309: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/persistence.feature:49:in `And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
Then all tps features but the first one are active 0.000
After features/support/hooks.rb:326 10.865 
SCENARIO FAILED: 'Booting Tails from a USB drive with an enabled persistent partition and reconfiguring it' (at time 04:11:58)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/04:11:58_Booting_Tails_from_a_USB_drive_with_an_enabled_persistent_partition_and_reconfiguring_it.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/04:11:58_Booting_Tails_from_a_USB_drive_with_an_enabled_persistent_partition_and_reconfiguring_it.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/04:11:58_Booting_Tails_from_a_USB_drive_with_an_enabled_persistent_partition_and_reconfiguring_it.journal
After features/support/hooks.rb:100 0.011
Feature: Using persistent Tor bridges and pluggable transports
5:34.141
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 11.998
And I create a persistent partition with the default settings 28.355
Then the "TorConfiguration" tps feature is not enabled 1.542
When the network is plugged 0.075
And the Tor Connection Assistant autostarts 9.645
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 11.817
And I wait until Tor is ready 4:30.707
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.747 
SCENARIO FAILED: 'Using Persistent Tor bridges' (at time 04:51:13)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/04:51:13_Using_Persistent_Tor_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/04:51:13_Using_Persistent_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/04:51:13_Using_Persistent_Tor_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/04:51:13_Using_Persistent_Tor_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/04:51:13_Using_Persistent_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/04:51:13_Using_Persistent_Tor_bridges.journal
After features/support/hooks.rb:100 0.000
Feature: Using persistent Tor bridges and pluggable transports
5:26.849
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.180
And I create a persistent partition with the default settings 24.223
Then the "TorConfiguration" tps feature is not enabled 1.404
When the network is plugged 0.098
And the Tor Connection Assistant autostarts 7.923
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 12.542
And I wait until Tor is ready 4:30.476
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 6.076 
SCENARIO FAILED: 'Disabling persistence of Tor bridges' (at time 04:56:46)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/04:56:46_Disabling_persistence_of_Tor_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/04:56:46_Disabling_persistence_of_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/04:56:46_Disabling_persistence_of_Tor_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/04:56:46_Disabling_persistence_of_Tor_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/04:56:46_Disabling_persistence_of_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/04:56:46_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.959
Scenario The Tor Browser cannot access the LAN
Before features/support/hooks.rb:269 0.008
Steps
Given I have started Tails from DVD and logged in and the network is connected 12.486
And a web server is running on the LAN 1.032
And I capture all network traffic 0.006
When I start the Tor Browser 25.545
And the Tor Browser loads the startup page 1.044
And I open a page on the LAN web server in the Tor Browser 10.844
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: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 5.551 
SCENARIO FAILED: 'The Tor Browser cannot access the LAN' (at time 05:18:37)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/05:18:37_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/5/artifact/build-artifacts/05:18:37_The_Tor_Browser_cannot_access_the_LAN.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/05:18:37_The_Tor_Browser_cannot_access_the_LAN.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/05:18:37_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:9.793
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.626
When I start the Tor Browser 28.021
And the Tor Browser loads the startup page 1.095
Then Tor Browser's circuit view is working 28.050
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.410 
SCENARIO FAILED: 'The Tor Browser's circuit view feature works as expected' (at time 05:28:31)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/05:28: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_feature-arti/5/artifact/build-artifacts/05:28:31_The_Tor_Browser_s_circuit_view_feature_works_as_expected.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/05:28:31_The_Tor_Browser_s_circuit_view_feature_works_as_expected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-arti/5/artifact/build-artifacts/05:28:31_The_Tor_Browser_s_circuit_view_feature_works_as_expected.journal
After features/support/hooks.rb:100 0.000