Project Number Date
test_Tails_ISO_19139-arti-bridges 20 03 Dec 2024, 22:01

Failures Overview

The following summary displays scenarios that failed.

Feature: Time syncing
Tags: @product @check_tor_leaks
5:0.738
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.259
When the network is plugged 0.145
And the Tor Connection Assistant autostarts 7.258
And I configure some normal bridges in the Tor Connection Assistant 14.386
And I wait until Tor is ready 4:30.687
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.035
After features/support/hooks.rb:326 5.207 
SCENARIO FAILED: 'Clock with host's time while using bridges' (at time 00:16:45)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/00:16:45_Clock_with_host_s_time_while_using_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/00:16:45_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/20/artifact/build-artifacts/00:16:45_Clock_with_host_s_time_while_using_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/00:16:45_Clock_with_host_s_time_while_using_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/00:16:45_Clock_with_host_s_time_while_using_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/00:16:45_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:57.661
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.003
Steps
Given I have started Tails from DVD without network and logged in 8.598
When I bump the system time with "+1 day" 0.269
And I capture all network traffic 0.005
And the network is plugged 0.081
And the Tor Connection Assistant autostarts 6.158
And I configure some obfs4 bridges in the Tor Connection Assistant in easy mode 12.064
And I wait until Tor is ready 4:30.483
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.033
After features/support/hooks.rb:326 5.196 
SCENARIO FAILED: 'Clock is one day in the future while using obfs4 bridges' (at time 00:21:48)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/00:21:48_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/20/artifact/build-artifacts/00:21:48_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/20/artifact/build-artifacts/00:21:48_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/20/artifact/build-artifacts/00:21:48_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/20/artifact/build-artifacts/00:21:48_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/20/artifact/build-artifacts/00:21:48_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.journal
After features/support/hooks.rb:100 0.030
Feature: Time syncing
Tags: @product @check_tor_leaks
5:28.999
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.003
Steps
Given I have started Tails from DVD without network and logged in 9.404
When I bump the system time with "+8 hours +15 minutes" 0.340
And all notifications have disappeared 4.209
And I capture all network traffic 0.004
And I make sure time sync before Tor connects fails 0.130
And the network is plugged 0.070
And the Tor Connection Assistant autostarts 4.932
When I configure the default bridges in the Tor Connection Assistant in easy mode without connecting 5.550
And I click "Connect to Tor" 1.210
And the Tor Connection Assistant fails to connect to Tor 16.427
# The "Fix Clock" button allows users to recover from this bug
Then I set the time zone in Tor Connection to "Asia/Shanghai" 15.006
Then the system clock is less than 20 minutes incorrect 0.281
When I click "Connect to Tor" 1.217
Then I wait until Tor is ready 4:30.212
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.035
After features/support/hooks.rb:326 5.328 
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:21)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/00:32:21_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/20/artifact/build-artifacts/00:32:21_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/20/artifact/build-artifacts/00:32:21_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/20/artifact/build-artifacts/00:32:21_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/20/artifact/build-artifacts/00:32:21_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/20/artifact/build-artifacts/00:32:21_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.042
Feature: Time syncing
Tags: @product @check_tor_leaks
5:23.095
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.002
Steps
Given I have started Tails from DVD without network and logged in 8.276
When I bump the system time with "+8 hours +15 minutes" 0.528
And all notifications have disappeared 4.020
And I capture all network traffic 0.002
And the network is plugged 0.076
And the Tor Connection Assistant autostarts 5.391
# 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.674
And I click "Connect to Tor" 1.182
Then the Tor Connection Assistant reports that it failed to connect 11.957
# The "Fix Clock" button allows users to recover from this bug
When I set the time zone in Tor Connection to "Asia/Shanghai" 14.984
Then the system clock is less than 20 minutes incorrect 0.243
# "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.372
When I click "Connect to Tor" 1.193
Then I wait until Tor is ready 4:30.189
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb: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.044
After features/support/hooks.rb:326 5.174 
SCENARIO FAILED: 'I can connect to obfs4 bridges having a clock East of UTC while hiding that I am using Tor' (at time 00:37:49)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/00:37:49_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/20/artifact/build-artifacts/00:37:49_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/20/artifact/build-artifacts/00:37:49_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/20/artifact/build-artifacts/00:37:49_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/20/artifact/build-artifacts/00:37:49_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/20/artifact/build-artifacts/00:37:49_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.040
Feature: Using Tor bridges and pluggable transports
Tags: @product
4:46.509
Scenario Using normal bridges
Steps
When I configure some normal bridges in the Tor Connection Assistant 15.743
Then I wait until Tor is ready 4:30.766
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb: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.224 
SCENARIO FAILED: 'Using normal bridges' (at time 00:43:23)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/00:43:23_Using_normal_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/00:43:23_Using_normal_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/00:43:23_Using_normal_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/00:43:23_Using_normal_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/00:43:23_Using_normal_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/00:43:23_Using_normal_bridges.journal
After features/support/hooks.rb:100 0.033
Feature: Using Tor bridges and pluggable transports
Tags: @product
4:43.326
Scenario Using obfs4 pluggable transports
Steps
When I configure some obfs4 bridges in the Tor Connection Assistant in hide mode 12.579
Then I wait until Tor is ready 4:30.746
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.379 
SCENARIO FAILED: 'Using obfs4 pluggable transports' (at time 00:48:25)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/00:48:25_Using_obfs4_pluggable_transports_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/00:48:25_Using_obfs4_pluggable_transports.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/00:48:25_Using_obfs4_pluggable_transports.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/00:48:25_Using_obfs4_pluggable_transports.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/00:48:25_Using_obfs4_pluggable_transports.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/00:48:25_Using_obfs4_pluggable_transports.journal
After features/support/hooks.rb:100 0.048
Feature: Using Tor bridges and pluggable transports
Tags: @product
5:9.387
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 38.865
Then I wait until Tor is ready 4:30.521
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.214 
SCENARIO FAILED: 'Using obfs4 pluggable transports from a QR code' (at time 00:53:53)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/00:53:53_Using_obfs4_pluggable_transports_from_a_QR_code_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/00:53:53_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/20/artifact/build-artifacts/00:53:53_Using_obfs4_pluggable_transports_from_a_QR_code.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/00:53:53_Using_obfs4_pluggable_transports_from_a_QR_code.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/00:53:53_Using_obfs4_pluggable_transports_from_a_QR_code.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/00:53:53_Using_obfs4_pluggable_transports_from_a_QR_code.journal
After features/support/hooks.rb:100 0.079
Feature: Using Tor bridges and pluggable transports
Tags: @product
5:28.141
Scenario TCA can scan QR code after a connection failure
Steps
Given the Tor network and default bridges are blocked 1.962
When I unsuccessfully configure a direct connection in the Tor Connection Assistant 31.810
Then the Tor Connection Assistant reports that it failed to connect 0.133
And tca.conf is empty 0.279
Given I scan a QR code from the error page in Tor Connection Assistant 22.226
And I retry connecting to Tor 1.186
Then I wait until Tor is ready 4:30.542
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.386 
SCENARIO FAILED: 'TCA can scan QR code after a connection failure' (at time 00:59:40)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/00:59:40_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/20/artifact/build-artifacts/00:59:40_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/20/artifact/build-artifacts/00:59:40_TCA_can_scan_QR_code_after_a_connection_failure.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/00:59:40_TCA_can_scan_QR_code_after_a_connection_failure.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/00:59:40_TCA_can_scan_QR_code_after_a_connection_failure.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/00:59:40_TCA_can_scan_QR_code_after_a_connection_failure.journal
After features/support/hooks.rb:100 0.035
Feature: Using Tor bridges and pluggable transports
Tags: @product @supports_real_tor
4:42.485
Scenario Default Tor bridges
Steps
When I configure the default bridges in the Tor Connection Assistant 11.940
Then I wait until Tor is ready 4:30.545
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.396 
SCENARIO FAILED: 'Default Tor bridges' (at time 01:04:44)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/01:04:44_Default_Tor_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/01:04:44_Default_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/01:04:44_Default_Tor_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/01:04:44_Default_Tor_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/01:04:44_Default_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/01:04:44_Default_Tor_bridges.journal
After features/support/hooks.rb:100 0.043
Feature: Using Tor bridges and pluggable transports
Tags: @product
4:54.632
Scenario Fall back to default bridges if failing to connect directly to the Tor network
Steps
Given the Tor network is blocked 2.462
When I configure a direct connection in the Tor Connection Assistant 21.569
Then I wait until Tor is ready 4:30.601
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.393 
SCENARIO FAILED: 'Fall back to default bridges if failing to connect directly to the Tor network' (at time 01:09:57)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/01:09:57_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/20/artifact/build-artifacts/01:09:57_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/20/artifact/build-artifacts/01:09:57_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/20/artifact/build-artifacts/01:09:57_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/20/artifact/build-artifacts/01:09:57_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/20/artifact/build-artifacts/01:09:57_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.journal
After features/support/hooks.rb:100 0.048
Feature: Using Tor bridges and pluggable transports
Tags: @product
4:58.923
Scenario Tor Connection honors my choice of using default bridges on retry, too
Steps
Given the Tor network and default bridges are blocked 2.515
When I unsuccessfully configure some default bridges in the Tor Connection Assistant 23.439
Then the Tor Connection Assistant reports that it failed to connect 0.117
Given the Tor network and default bridges are unblocked 1.479
When I click "Connect to Tor" 1.157
Then I wait until Tor is ready 4:30.214
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.533 
SCENARIO FAILED: 'Tor Connection honors my choice of using default bridges on retry, too' (at time 01:20:19)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/01:20:19_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/20/artifact/build-artifacts/01:20:19_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/20/artifact/build-artifacts/01:20:19_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/20/artifact/build-artifacts/01:20:19_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/20/artifact/build-artifacts/01:20:19_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/20/artifact/build-artifacts/01:20:19_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:2.640
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.184
And I create a 7200 MiB disk named "old" 0.051
And I plug USB drive "old" 1.061
And I write an old version of the Tails USB image to disk "old" 30.379
When I start Tails from USB drive "old" with network unplugged 1:30.963
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.785 
SCENARIO FAILED: 'Installing an old version of Tails to a pristine USB drive' (at time 02:24:17)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/02:24:17_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/20/artifact/build-artifacts/02:24:17_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/20/artifact/build-artifacts/02:24:17_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/20/artifact/build-artifacts/02:24:17_Installing_an_old_version_of_Tails_to_a_pristine_USB_drive.journal
After features/support/hooks.rb:100 0.007
Feature: Upgrading an old Tails USB installation
Tags: @product
1:4.066
Scenario Creating a persistent partition with the old Tails USB installation
Before features/support/hooks.rb:269 0.003
Steps
Given a computer 0.182
And I start Tails from USB drive "old" with network unplugged and I login 1:3.884
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.809 
SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 02:25:26)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/02:25:26_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/20/artifact/build-artifacts/02:25:26_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/02:25:26_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/20/artifact/build-artifacts/02:25:26_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
59.623
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.188
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 59.434
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.894 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 02:26:30)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/02:26:30_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/20/artifact/build-artifacts/02:26:30_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/20/artifact/build-artifacts/02:26:30_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/20/artifact/build-artifacts/02:26:30_Writing_files_to_a_read_write-enabled_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
1:15.854
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:269 0.004
Steps
Given a computer 0.207
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:15.647
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.388 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 02:30:27)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/02:30:27_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/20/artifact/build-artifacts/02:30:27_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/20/artifact/build-artifacts/02:30:27_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/20/artifact/build-artifacts/02:30:27_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:100 0.008
Feature: Packages are up-to-date
Tags: @source
10.356
Scenario All packages are up-to-date
Before features/support/hooks.rb:528 0.000
Steps
Given I have the build manifest for the image under test 0.000
Then all packages listed in the build manifest are up-to-date 10.356
Command 
Command failed (pid 52973 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_19139-arti-bridges/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_19139-arti-bridges/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_19139-arti-bridges/tmp/tails-amd64-19139-arti-bridges@a8e152a393+stable@f7725cad33-20241203T1603Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_19139-arti-bridges/tmp/tails-amd64-19139-arti-bridges@a8e152a393+stable@f7725cad33-20241203T1603Z.build-manifest
INFO: Need to upgrade to a new APT snapshot:
  - blinker (1.8.2-1) to Debian trixie (1.9.0-1)
  - firmware-sof (2024.06-2) to Debian trixie (2024.09.1-1)
  - flask (3.0.3-1) to Debian trixie (3.1.0-2)
  - python-werkzeug (3.0.4-1) to Debian trixie (3.1.3-2)
 (CommandFailed)
/var/lib/jenkins/workspace/test_Tails_ISO_19139-arti-bridges/features/support/helpers/misc_helpers.rb:332:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_19139-arti-bridges/features/support/helpers/misc_helpers.rb:325:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_19139-arti-bridges/features/support/helpers/misc_helpers.rb:325:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_19139-arti-bridges/features/step_definitions/needed_package_updates.rb:8:in `/^all packages listed in the build manifest are up-to-date$/'
features/needed_package_updates.feature:12:in `Then all packages listed in the build manifest are up-to-date'
After features/support/hooks.rb:535 0.000
After features/support/hooks.rb:100 0.000
Feature: Using persistent Tor bridges and pluggable transports
5:41.144
Background
Before features/support/hooks.rb:269 0.005
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 25.204
And I create a persistent partition with the default settings 21.797
Then the "TorConfiguration" tps feature is not enabled 1.176
When the network is plugged 0.082
And the Tor Connection Assistant autostarts 11.966
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 10.354
And I wait until Tor is ready 4:30.563
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.617 
SCENARIO FAILED: 'Using Persistent Tor bridges' (at time 04:24:41)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/04:24:41_Using_Persistent_Tor_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/04:24:41_Using_Persistent_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/04:24:41_Using_Persistent_Tor_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/04:24:41_Using_Persistent_Tor_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/04:24:41_Using_Persistent_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/04:24:41_Using_Persistent_Tor_bridges.journal
After features/support/hooks.rb:100 0.000
Feature: Using persistent Tor bridges and pluggable transports
5:25.118
Background
Before features/support/hooks.rb:269 0.005
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 9.255
And I create a persistent partition with the default settings 24.682
Then the "TorConfiguration" tps feature is not enabled 1.318
When the network is plugged 0.065
And the Tor Connection Assistant autostarts 9.040
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 10.177
And I wait until Tor is ready 4:30.578
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.317 
SCENARIO FAILED: 'Disabling persistence of Tor bridges' (at time 04:30:12)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/04:30:12_Disabling_persistence_of_Tor_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/04:30:12_Disabling_persistence_of_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/04:30:12_Disabling_persistence_of_Tor_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/04:30:12_Disabling_persistence_of_Tor_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/04:30:12_Disabling_persistence_of_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/04:30:12_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:46.577
Scenario The Tor Browser cannot access the LAN
Before features/support/hooks.rb:269 0.020
Steps
Given I have started Tails from DVD and logged in and the network is connected 11.230
And a web server is running on the LAN 1.033
And I capture all network traffic 0.006
When I start the Tor Browser 23.791
And the Tor Browser loads the startup page 0.889
And I open a page on the LAN web server in the Tor Browser 9.624
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 10.682 
SCENARIO FAILED: 'The Tor Browser cannot access the LAN' (at time 04:49:44)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/04:49:44_The_Tor_Browser_cannot_access_the_LAN.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/04:49:44_The_Tor_Browser_cannot_access_the_LAN.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/04:49:44_The_Tor_Browser_cannot_access_the_LAN.journal
After features/support/hooks.rb:100 0.042
Feature: Browsing the web using the Tor Browser
Tags: @product
1:3.810
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.270
When I start the Tor Browser 23.258
And the Tor Browser loads the startup page 1.003
Then Tor Browser's circuit view is working 27.276
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.361 
SCENARIO FAILED: 'The Tor Browser's circuit view feature works as expected' (at time 04:58:22)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/04:58:22_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/20/artifact/build-artifacts/04:58:22_The_Tor_Browser_s_circuit_view_feature_works_as_expected.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_19139-arti-bridges/20/artifact/build-artifacts/04:58:22_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/20/artifact/build-artifacts/04:58:22_The_Tor_Browser_s_circuit_view_feature_works_as_expected.journal
After features/support/hooks.rb:100 0.000