Project Number Date
test_Tails_ISO_20297-debug-proxy-refusing-connections 110 03 Jul 2025, 20:51

Failures Overview

The following summary displays scenarios that failed.

Feature: Time syncing
Tags: @product @check_tor_leaks
10:9.564
Scenario Clock with host's time
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.029
Before features/support/hooks.rb:512 0.026
Steps
Given I have started Tails from DVD without network and logged in 8.535
When the network is plugged 10:1.029
Command 
Command failed (pid 6111 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20297-debug-proxy-refusing-connections/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_20297-debug-proxy-refusing-connections/features/chutney/test-network", {:err=>[:child, :out]}]
Bootstrap failed: 600 seconds
Node status:
test000auth  :  100, done                     , Done
test001auth  :  100, done                     , Done
test002auth  :  100, done                     , Done
test003auth  :  100, done                     , Done
test004ba    :  100, done                     , Done
test005relay :  100, done                     , Done
test006relay :  100, done                     , Done
test007relay :  100, done                     , Done
test008relay :  100, done                     , Done
test009relay :  100, done                     , Done
test010relay :  100, done                     , Done
test011relay :  100, done                     , Done
chutney.errors.ChutneyTimeoutError
test012relay :  100, done                     , Done
test013relay :  100, done                     , Done
test014relay :  100, done                     , Done
test015relay :  100, done                     , Done
test016relay :  100, done                     , Done
test017relay :  100, done                     , Done
test018relay :  100, done                     , Done
test019relay :  100, done                     , Done
test020bridge:  100, done                     , Done
test021bridge:  100, done                     , Done
test022obfs4 :  100, done                     , Done
test023obfs4 :  100, done                     , Done
test024defbr :  100, done                     , Done
test025client:  100, done                     , Done
Published dir info:
test000auth  :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test001auth  :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test002auth  :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test003auth  :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test004ba    :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test005relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test006relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test007relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test008relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test009relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test010relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test011relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test012relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test013relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test014relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test015relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test016relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test017relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test018relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test019relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test020bridge:  100, 004ba                    , desc                          , Dir info cached
test021bridge:  100, 004ba                    , desc                          , Dir info cached
test022obfs4 :  100, 004ba                    , desc                          , Dir info cached
test023obfs4 :  100, 004ba                    , desc                          , Dir info cached
test024defbr :    0, 004ba                    , desc                          , Not in dir file

 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/time_syncing.feature:9:in `When the network is plugged'
And I successfully configure Tor 0.000
Then the system clock is less than 5 minutes incorrect 0.000
After features/support/hooks.rb:520 0.058
After features/support/hooks.rb:335 6.560 
SCENARIO FAILED: 'Clock with host's time' (at time 00:21:47)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:21:47_Clock_with_host_s_time_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:21:47_Clock_with_host_s_time.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:21:47_Clock_with_host_s_time.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:21:47_Clock_with_host_s_time.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:21:47_Clock_with_host_s_time.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:21:47_Clock_with_host_s_time.journal
After features/support/hooks.rb:105 0.000
Feature: Time syncing
Tags: @product @check_tor_leaks
10:9.004
Scenario Clock with host's time while using bridges
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.002
Before features/support/hooks.rb:512 0.002
Steps
Given I have started Tails from DVD without network and logged in 8.552
When the network is plugged 10:0.452
Command 
Command failed (pid 6272 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20297-debug-proxy-refusing-connections/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_20297-debug-proxy-refusing-connections/features/chutney/test-network", {:err=>[:child, :out]}]
Bootstrap failed: 600 seconds
Node status:
test000auth  :  100, done                     , Done
test001auth  :  100, done                     , Done
test002auth  :  100, done                     , Done
test003auth  :  100, done                     , Done
test004ba    :  100, done                     , Done
test005relay :  100, done                     , Done
test006relay :  100, done                     , Done
test007relay :  100, done                     , Done
test008relay :  100, done                     , Done
test009relay :  100, done                     , Done
test010relay :  100, done                     , Done
test011relay :  100, done                     , Done
chutney.errors.ChutneyTimeoutError
test012relay :  100, done                     , Done
test013relay :  100, done                     , Done
test014relay :  100, done                     , Done
test015relay :  100, done                     , Done
test016relay :  100, done                     , Done
test017relay :  100, done                     , Done
test018relay :  100, done                     , Done
test019relay :  100, done                     , Done
test020bridge:  100, done                     , Done
test021bridge:  100, done                     , Done
test022obfs4 :  100, done                     , Done
test023obfs4 :  100, done                     , Done
test024defbr :  100, done                     , Done
test025client:  100, done                     , Done
Published dir info:
test000auth  :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test001auth  :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test002auth  :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test003auth  :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test004ba    :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test005relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test006relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test007relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test008relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test009relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test010relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test011relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test012relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test013relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test014relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test015relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test016relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test017relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test018relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test019relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test020bridge:  100, 004ba                    , desc                          , Dir info cached
test021bridge:  100, 004ba                    , desc                          , Dir info cached
test022obfs4 :  100, 004ba                    , desc                          , Dir info cached
test023obfs4 :  100, 004ba                    , desc                          , Dir info cached
test024defbr :    0, 004ba                    , desc                          , Not in dir file

 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/time_syncing.feature:15:in `When the network is plugged'
And the Tor Connection Assistant autostarts 0.000
And I configure some normal bridges in the Tor Connection Assistant 0.000
And I wait until Tor is ready 0.000
Then the system clock is less than 5 minutes incorrect 0.000
After features/support/hooks.rb:520 0.049
After features/support/hooks.rb:335 6.354 
SCENARIO FAILED: 'Clock with host's time while using bridges' (at time 00:32:03)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:32:03_Clock_with_host_s_time_while_using_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:32:03_Clock_with_host_s_time_while_using_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:32:03_Clock_with_host_s_time_while_using_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:32:03_Clock_with_host_s_time_while_using_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:32:03_Clock_with_host_s_time_while_using_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:32:03_Clock_with_host_s_time_while_using_bridges.journal
After features/support/hooks.rb:105 0.000
Feature: Time syncing
Tags: @product @check_tor_leaks
10:11.244
Scenario Clock is one day in the future while using obfs4 bridges
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.102
Before features/support/hooks.rb:512 0.081
Steps
Given I have started Tails from DVD without network and logged in 10.570
When I bump the system time with "+1 day" 0.287
And I capture all network traffic 0.002
And the network is plugged 10:0.383
Command 
Command failed (pid 6439 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20297-debug-proxy-refusing-connections/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_20297-debug-proxy-refusing-connections/features/chutney/test-network", {:err=>[:child, :out]}]
Bootstrap failed: 600 seconds
Node status:
test000auth  :  100, done                     , Done
test001auth  :  100, done                     , Done
test002auth  :  100, done                     , Done
test003auth  :  100, done                     , Done
test004ba    :  100, done                     , Done
test005relay :  100, done                     , Done
test006relay :  100, done                     , Done
test007relay :  100, done                     , Done
test008relay :  100, done                     , Done
test009relay :  100, done                     , Done
test010relay :  100, done                     , Done
test011relay :  100, done                     , Done
test012relay :  100, done                     , Done
test013relay :  100, done                     , Done
test014relay :  100, done                     , Done
test015relay :  100, done                     , Done
test016relay :  100, done                     , Done
test017relay :  100, done                     , Done
test018relay :  100, done                     , Done
test019relay :  100, done                     , Done
test020bridge:  100, done                     , Done
test021bridge:  100, done                     , Done
test022obfs4 :  100, done                     , Done
test023obfs4 :  100, done                     , Done
test024defbr :  100, done                     , Done
test025client:  100, done                     , Done
Published dir info:
test000auth  :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test001auth  :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test002auth  :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test003auth  :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test004ba    :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test005relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test006relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test007relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test008relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test009relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test010relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test011relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test012relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test013relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test014relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test015relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test016relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test017relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test018relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test019relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test020bridge:  100, 004ba                    , desc                          , Dir info cached
test021bridge:  100, 004ba                    , desc                          , Dir info cached
test022obfs4 :  100, 004ba                    , desc                          , Dir info cached
test023obfs4 :  100, 004ba                    , desc                          , Dir info cached
test024defbr :    0, 004ba                    , desc                          , Not in dir file

 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/time_syncing.feature:25:in `And the network is plugged'
And the Tor Connection Assistant autostarts 0.000
And I configure some obfs4 bridges in the Tor Connection Assistant in easy mode 0.000
And I wait until Tor is ready 0.000
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:520 0.041
After features/support/hooks.rb:335 6.382 
SCENARIO FAILED: 'Clock is one day in the future while using obfs4 bridges' (at time 00:42:21)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:42:21_Clock_is_one_day_in_the_future_while_using_obfs4_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:42:21_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_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:42:21_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:42:21_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:42:21_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:42:21_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.journal
After features/support/hooks.rb:105 0.043
Feature: Time syncing
Tags: @product @check_tor_leaks
1:50.612
Scenario On a clock with host's time, Tor Connection works even if time sync fails
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.002
Before features/support/hooks.rb:512 0.003
Steps
Given I have started Tails from DVD without network and logged in 11.848
And I make sure time sync before Tor connects times out 1.246
When the network is plugged 1:37.516
Command 
Command failed (pid 7293 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20297-debug-proxy-refusing-connections/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_20297-debug-proxy-refusing-connections/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/time_syncing.feature:58:in `When the network is plugged'
And I successfully configure Tor 0.000
Then the system clock is less than 5 minutes incorrect 0.000
After features/support/hooks.rb:520 0.054
After features/support/hooks.rb:335 5.961 
SCENARIO FAILED: 'On a clock with host's time, Tor Connection works even if time sync fails' (at time 00:48:55)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:48:55_On_a_clock_with_host_s_time,_Tor_Connection_works_even_if_time_sync_fails_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:48:55_On_a_clock_with_host_s_time,_Tor_Connection_works_even_if_time_sync_fails.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:48:55_On_a_clock_with_host_s_time,_Tor_Connection_works_even_if_time_sync_fails.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:48:55_On_a_clock_with_host_s_time,_Tor_Connection_works_even_if_time_sync_fails.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:48:55_On_a_clock_with_host_s_time,_Tor_Connection_works_even_if_time_sync_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:48:55_On_a_clock_with_host_s_time,_Tor_Connection_works_even_if_time_sync_fails.journal
After features/support/hooks.rb:105 0.001
Feature: Time syncing
Tags: @product @check_tor_leaks
5:33.526
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:271 0.000
Before features/support/hooks.rb:278 0.003
Before features/support/hooks.rb:512 0.003
Steps
Given I have started Tails from DVD without network and logged in 11.965
When I bump the system time with "+8 hours +15 minutes" 0.561
And all notifications have disappeared 5.363
And I capture all network traffic 0.002
And I make sure time sync before Tor connects fails 0.129
And the network is plugged 5:15.503
Command 
Command failed (pid 7449 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20297-debug-proxy-refusing-connections/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_20297-debug-proxy-refusing-connections/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/time_syncing.feature:68:in `And the network is plugged'
And the Tor Connection Assistant autostarts 0.000
When I configure the default bridges in the Tor Connection Assistant in easy mode without connecting 0.000
And I click "Connect to Tor" 0.000
And the Tor Connection Assistant fails to connect to Tor 0.000
# The "Fix Clock" button allows users to recover from this bug
Then I set the time zone in Tor Connection to "Asia/Shanghai" 0.000
Then the system clock is less than 20 minutes incorrect 0.000
When I click "Connect to Tor" 0.000
Then I wait until Tor is ready 0.000
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:520 0.031
After features/support/hooks.rb:335 5.951 
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:54:35)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:54:35_I_can_manually_recover_from_time_sync_failure_when_connecting_automatically_to_obfs4_bridges_with_a_clock_East_of_UTC_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:54:35_I_can_manually_recover_from_time_sync_failure_when_connecting_automatically_to_obfs4_bridges_with_a_clock_East_of_UTC.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:54:35_I_can_manually_recover_from_time_sync_failure_when_connecting_automatically_to_obfs4_bridges_with_a_clock_East_of_UTC.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:54:35_I_can_manually_recover_from_time_sync_failure_when_connecting_automatically_to_obfs4_bridges_with_a_clock_East_of_UTC.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:54:35_I_can_manually_recover_from_time_sync_failure_when_connecting_automatically_to_obfs4_bridges_with_a_clock_East_of_UTC.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:54:35_I_can_manually_recover_from_time_sync_failure_when_connecting_automatically_to_obfs4_bridges_with_a_clock_East_of_UTC.journal
After features/support/hooks.rb:105 0.055
Feature: Time syncing
Tags: @product @check_tor_leaks
2:14.687
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:271 0.000
Before features/support/hooks.rb:278 0.003
Before features/support/hooks.rb:512 0.002
Steps
Given I have started Tails from DVD without network and logged in 9.838
When I bump the system time with "+8 hours +15 minutes" 1.078
And all notifications have disappeared 5.373
And I capture all network traffic 0.002
And the network is plugged 1:58.394
Command 
Command failed (pid 8182 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20297-debug-proxy-refusing-connections/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_20297-debug-proxy-refusing-connections/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/time_syncing.feature:87:in `And the network is plugged'
And the Tor Connection Assistant autostarts 0.000
# 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 0.000
And I click "Connect to Tor" 0.000
Then the Tor Connection Assistant reports that it failed to connect 0.000
# The "Fix Clock" button allows users to recover from this bug
When I set the time zone in Tor Connection to "Asia/Shanghai" 0.000
Then the system clock is less than 20 minutes incorrect 0.000
# "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.000
When I click "Connect to Tor" 0.000
Then I wait until Tor is ready 0.000
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:520 0.032
After features/support/hooks.rb:335 6.204 
SCENARIO FAILED: 'I can connect to obfs4 bridges having a clock East of UTC while hiding that I am using Tor' (at time 00:56:56)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:56:56_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_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:56:56_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_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:56:56_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_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:56:56_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_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:56:56_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_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:56:56_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:105 0.029
Feature: Time syncing
Tags: @product @check_tor_leaks
1:12.697
Scenario Time sync before Tor connects sets the same headers as the NetworkManager connectivity check
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.003
Before features/support/hooks.rb:512 0.003
Steps
Given I have started Tails from DVD without network and logged in 13.771
And I make sure time sync before Tor connects uses a fake connectivity check service 1.263
And the network is plugged 57.662
Command 
Command failed (pid 8340 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20297-debug-proxy-refusing-connections/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_20297-debug-proxy-refusing-connections/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/time_syncing.feature:108:in `And the network is plugged'
And Tor is ready 0.000
Then the fake connectivity check service has received a new HTTP request 0.000
When I make NetworkManager perform a connectivity check 0.000
Then the fake connectivity check service has received a new HTTP request 0.000
And the HTTP requests received by the fake connectivity check service are identical 0.000
After features/support/hooks.rb:520 0.034
After features/support/hooks.rb:335 5.913 
SCENARIO FAILED: 'Time sync before Tor connects sets the same headers as the NetworkManager connectivity check' (at time 00:58:15)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:58:15_Time_sync_before_Tor_connects_sets_the_same_headers_as_the_NetworkManager_connectivity_check_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:58:15_Time_sync_before_Tor_connects_sets_the_same_headers_as_the_NetworkManager_connectivity_check.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:58:15_Time_sync_before_Tor_connects_sets_the_same_headers_as_the_NetworkManager_connectivity_check.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:58:15_Time_sync_before_Tor_connects_sets_the_same_headers_as_the_NetworkManager_connectivity_check.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:58:15_Time_sync_before_Tor_connects_sets_the_same_headers_as_the_NetworkManager_connectivity_check.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:58:15_Time_sync_before_Tor_connects_sets_the_same_headers_as_the_NetworkManager_connectivity_check.journal
After features/support/hooks.rb:105 0.000
Feature: Using Tor bridges and pluggable transports
1:35.652
Background
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.003
Steps
Given I have started Tails from DVD without network and logged in 9.508
And I capture all network traffic 0.128
When the network is plugged 1:26.015
Command 
Command failed (pid 8491 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20297-debug-proxy-refusing-connections/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_20297-debug-proxy-refusing-connections/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/tor_bridges.feature:10:in `When the network is plugged'
Then the Tor Connection Assistant autostarts 0.000
Feature: Using Tor bridges and pluggable transports
Tags: @product
0.000
Scenario Using normal bridges
Steps
When I configure some normal bridges in the Tor Connection Assistant 0.000
Then I wait until Tor is ready 0.000
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:335 5.769 
SCENARIO FAILED: 'Using normal bridges' (at time 00:59:57)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:59:57_Using_normal_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:59:57_Using_normal_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:59:57_Using_normal_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:59:57_Using_normal_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:59:57_Using_normal_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/00:59:57_Using_normal_bridges.journal
After features/support/hooks.rb:105 0.052
Feature: Using Tor bridges and pluggable transports
54.861
Background
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.002
Steps
Given I have started Tails from DVD without network and logged in 12.561
And I capture all network traffic 0.004
When the network is plugged 42.296
Command 
Command failed (pid 8644 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20297-debug-proxy-refusing-connections/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_20297-debug-proxy-refusing-connections/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/tor_bridges.feature:10:in `When the network is plugged'
Then the Tor Connection Assistant autostarts 0.000
Feature: Using Tor bridges and pluggable transports
Tags: @product
0.000
Scenario Using obfs4 pluggable transports
Steps
When I configure some obfs4 bridges in the Tor Connection Assistant in hide mode 0.000
Then I wait until Tor is ready 0.000
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:335 5.876 
SCENARIO FAILED: 'Using obfs4 pluggable transports' (at time 01:00:57)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/01:00:57_Using_obfs4_pluggable_transports_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/01:00:57_Using_obfs4_pluggable_transports.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/01:00:57_Using_obfs4_pluggable_transports.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/01:00:57_Using_obfs4_pluggable_transports.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/01:00:57_Using_obfs4_pluggable_transports.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/01:00:57_Using_obfs4_pluggable_transports.journal
After features/support/hooks.rb:105 0.072
Feature: Using Tor bridges and pluggable transports
35.676
Background
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.003
Steps
Given I have started Tails from DVD without network and logged in 13.994
And I capture all network traffic 0.015
When the network is plugged 21.665
Command 
Command failed (pid 8797 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20297-debug-proxy-refusing-connections/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_20297-debug-proxy-refusing-connections/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/tor_bridges.feature:10:in `When the network is plugged'
Then the Tor Connection Assistant autostarts 0.000
Feature: Using Tor bridges and pluggable transports
Tags: @product
0.000
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 0.000
Then I wait until Tor is ready 0.000
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:335 6.111 
SCENARIO FAILED: 'Using obfs4 pluggable transports from a QR code' (at time 01:01:39)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/01:01:39_Using_obfs4_pluggable_transports_from_a_QR_code_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/01:01:39_Using_obfs4_pluggable_transports_from_a_QR_code.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/01:01:39_Using_obfs4_pluggable_transports_from_a_QR_code.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/01:01:39_Using_obfs4_pluggable_transports_from_a_QR_code.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/01:01:39_Using_obfs4_pluggable_transports_from_a_QR_code.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/01:01:39_Using_obfs4_pluggable_transports_from_a_QR_code.journal
After features/support/hooks.rb:105 0.037
Feature: Using Tor bridges and pluggable transports
51.144
Background
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.002
Steps
Given I have started Tails from DVD without network and logged in 13.581
And I capture all network traffic 0.011
When the network is plugged 37.551
Command 
Command failed (pid 8946 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20297-debug-proxy-refusing-connections/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_20297-debug-proxy-refusing-connections/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/tor_bridges.feature:10:in `When the network is plugged'
Then the Tor Connection Assistant autostarts 0.000
Feature: Using Tor bridges and pluggable transports
Tags: @product
0.000
Scenario TCA can scan QR code after a connection failure
Steps
Given the Tor network and default bridges are blocked 0.000
When I unsuccessfully configure a direct connection in the Tor Connection Assistant 0.000
Then the Tor Connection Assistant reports that it failed to connect 0.000
And tca.conf is empty 0.000
Given I scan a QR code from the error page in Tor Connection Assistant 0.000
And I retry connecting to Tor 0.000
Then I wait until Tor is ready 0.000
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:335 5.897 
SCENARIO FAILED: 'TCA can scan QR code after a connection failure' (at time 01:02:36)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/01:02:36_TCA_can_scan_QR_code_after_a_connection_failure_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/01:02:36_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_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/01:02:36_TCA_can_scan_QR_code_after_a_connection_failure.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/01:02:36_TCA_can_scan_QR_code_after_a_connection_failure.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/01:02:36_TCA_can_scan_QR_code_after_a_connection_failure.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/01:02:36_TCA_can_scan_QR_code_after_a_connection_failure.journal
After features/support/hooks.rb:105 0.032
Feature: Using Tor bridges and pluggable transports
34.712
Background
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.002
Steps
Given I have started Tails from DVD without network and logged in 24.168
And I capture all network traffic 0.005
When the network is plugged 10.538
Command 
Command failed (pid 9209 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20297-debug-proxy-refusing-connections/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_20297-debug-proxy-refusing-connections/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/tor_bridges.feature:10:in `When the network is plugged'
Then the Tor Connection Assistant autostarts 0.000
Feature: Using Tor bridges and pluggable transports
Tags: @product @supports_real_tor
0.000
Scenario Default Tor bridges
Steps
When I configure the default bridges in the Tor Connection Assistant 0.000
Then I wait until Tor is ready 0.000
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:335 6.074 
SCENARIO FAILED: 'Default Tor bridges' (at time 01:03:17)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/01:03:17_Default_Tor_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/01:03:17_Default_Tor_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/01:03:17_Default_Tor_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/01:03:17_Default_Tor_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/01:03:17_Default_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/01:03:17_Default_Tor_bridges.journal
After features/support/hooks.rb:105 0.050
Feature: Using Tor bridges and pluggable transports
1:33.056
Background
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.004
Steps
Given I have started Tails from DVD without network and logged in 14.655
And I capture all network traffic 0.004
When the network is plugged 1:18.396
Command 
Command failed (pid 9359 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20297-debug-proxy-refusing-connections/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_20297-debug-proxy-refusing-connections/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/tor_bridges.feature:10:in `When the network is plugged'
Then the Tor Connection Assistant autostarts 0.000
Feature: Using Tor bridges and pluggable transports
Tags: @product
0.000
Scenario Fall back to default bridges if failing to connect directly to the Tor network
Steps
Given the Tor network is blocked 0.000
When 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 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:335 5.999 
SCENARIO FAILED: 'Fall back to default bridges if failing to connect directly to the Tor network' (at time 01:04:56)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/01:04:56_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_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/01:04:56_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_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/01:04:56_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_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/01:04:56_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_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/01:04:56_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_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/01:04:56_Fall_back_to_default_bridges_if_failing_to_connect_directly_to_the_Tor_network.journal
After features/support/hooks.rb:105 0.040
Feature: Using Tor bridges and pluggable transports
10:24.206
Background
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.002
Steps
Given I have started Tails from DVD without network and logged in 23.371
And I capture all network traffic 0.008
When the network is plugged 10:0.826
Command 
Command failed (pid 9625 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20297-debug-proxy-refusing-connections/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_20297-debug-proxy-refusing-connections/features/chutney/test-network", {:err=>[:child, :out]}]
Bootstrap failed: 600 seconds
Node status:
test000auth  :  100, done                     , Done
test001auth  :  100, done                     , Done
test002auth  :  100, done                     , Done
test003auth  :  100, done                     , Done
test004ba    :  100, done                     , Done
test005relay :  100, done                     , Done
test006relay :  100, done                     , Done
test007relay :  100, done                     , Done
test008relay :  100, done                     , Done
test009relay :  100, done                     , Done
test010relay :  100, done                     , Done
test011relay :  100, done                     , Done
test012relay :  100, done                     , Done
test013relay :  100, done                     , Done
test014relay :  100, done                     , Done
test015relay :  100, done                     , Done
test016relay :  100, done                     , Done
test017relay :  100, done                     , Done
test018relay :  100, done                     , Done
test019relay :  100, done                     , Done
test020bridge:  100, done                     , Done
test021bridge:  100, done                     , Done
test022obfs4 :  100, done                     , Done
test023obfs4 :  100, done                     , Done
test024defbr :  100, done                     , Done
test025client:  100, done                     , Done
Published dir info:
test000auth  :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test001auth  :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test002auth  :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test003auth  :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test004ba    :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test005relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test006relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test007relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test008relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test009relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test010relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test011relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test012relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test013relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test014relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test015relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test016relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test017relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test018relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test019relay :  100, all nodes                , desc md md_cons ns_cons       , Dir info cached
test020bridge:  100, 004ba                    , desc                          , Dir info cached
test021bridge:  100, 004ba                    , desc                          , Dir info cached
test022obfs4 :  100, 004ba                    , desc                          , Dir info cached
test023obfs4 :  100, 004ba                    , desc                          , Dir info cached
test024defbr :    0, 004ba                    , desc                          , Not in dir file

 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/tor_bridges.feature:10:in `When the network is plugged'
Then the Tor Connection Assistant autostarts 0.000
Feature: Using Tor bridges and pluggable transports
Tags: @product
0.000
Scenario TCA can reconnect after a connection failure
Steps
Given the Tor network and default bridges are blocked 0.000
When I unsuccessfully configure a direct connection in the Tor Connection Assistant 0.000
Then the Tor Connection Assistant reports that it failed to connect 0.000
And tca.conf is empty 0.000
Given the Tor network and default bridges are unblocked 0.000
And I retry connecting to Tor 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes no bridge 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through Tor or connectivity check service 0.000
After features/support/hooks.rb:335 6.907 
SCENARIO FAILED: 'TCA can reconnect after a connection failure' (at time 01:15:27)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/01:15:27_TCA_can_reconnect_after_a_connection_failure_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/01:15:27_TCA_can_reconnect_after_a_connection_failure.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/01:15:27_TCA_can_reconnect_after_a_connection_failure.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/01:15:27_TCA_can_reconnect_after_a_connection_failure.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/01:15:27_TCA_can_reconnect_after_a_connection_failure.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/01:15:27_TCA_can_reconnect_after_a_connection_failure.journal
After features/support/hooks.rb:105 0.045
Feature: Using Tor bridges and pluggable transports
9:3.059
Background
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.002
Steps
Given I have started Tails from DVD without network and logged in 9.014
And I capture all network traffic 0.008
When the network is plugged 8:54.036
Command 
Command failed (pid 9791 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20297-debug-proxy-refusing-connections/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_20297-debug-proxy-refusing-connections/features/chutney/test-network", {:err=>[:child, :out]}]
 (ChutneyBootstrapFailure)
./features/step_definitions/chutney.rb:169:in `rescue in wait_until_chutney_is_working'
./features/step_definitions/chutney.rb:163:in `wait_until_chutney_is_working'
./features/step_definitions/common_steps.rb:175:in `/^the network is plugged$/'
features/tor_bridges.feature:10:in `When the network is plugged'
Then the Tor Connection Assistant autostarts 0.000
Feature: Using Tor bridges and pluggable transports
Tags: @product
0.000
Scenario Normal bridges are not allowed in "Hide" mode
Steps
When I try to configure some normal bridges in the Tor Connection Assistant in hide mode 0.000
Then the Tor Connection Assistant complains that normal bridges are not allowed 0.000
And I cannot click the "Connect to Tor" button 0.000
After features/support/hooks.rb:335 5.942 
SCENARIO FAILED: 'Normal bridges are not allowed in "Hide" mode' (at time 01:24:36)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/01:24:36_Normal_bridges_are_not_allowed_in__Hide__mode_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/01:24:36_Normal_bridges_are_not_allowed_in__Hide__mode.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/01:24:36_Normal_bridges_are_not_allowed_in__Hide__mode.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/01:24:36_Normal_bridges_are_not_allowed_in__Hide__mode.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/01:24:36_Normal_bridges_are_not_allowed_in__Hide__mode.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/01:24:36_Normal_bridges_are_not_allowed_in__Hide__mode.journal
After features/support/hooks.rb:105 0.052
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited
21:58.384
Scenario I am notified when Additional Software fails to install a package
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.016
Before features/support/hooks.rb:512 0.012
Steps
Given a computer 0.239
And I start Tails from USB drive "__internal" with network unplugged 1:8.278
And I enable persistence 16.271
And I remove the "cowsay" deb files from the APT cache 0.067
# Prevent the "Warning: virtual machine detected!" notification from racing
# with the one we'll be interacting with below.
And I disable the tails-virt-notify-user.service user unit 0.091
And I log in to a new session 32.483
Then I see the "The installation of your additional software failed" notification after at most 300 seconds 20:0.951
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:595:in `new'
./features/step_definitions/common_steps.rb:595:in `/^I see the "(.+)" notification(?: after at most (\d+) seconds)?$/'
features/additional_software_packages.feature:129:in `Then I see the "The installation of your additional software failed" notification after at most 300 seconds'
And I can open the Additional Software log file from the notification 0.000
And the package "cowsay" is not installed 0.000
After features/support/hooks.rb:520 0.051
After features/support/hooks.rb:335 11.035 
SCENARIO FAILED: 'I am notified when Additional Software fails to install a package' (at time 02:55:52)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/02:55:52_I_am_notified_when_Additional_Software_fails_to_install_a_package.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/02:55:52_I_am_notified_when_Additional_Software_fails_to_install_a_package.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/02:55:52_I_am_notified_when_Additional_Software_fails_to_install_a_package.journal
After features/support/hooks.rb:105 0.008
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
47.859
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.017
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 12.034
When I log in to a new session in English (en) 24.093
Then the keyboard layout is set to "us" 0.201
When the network is plugged 0.091
And Tor is ready 11.437
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:502:in `tca_configure'
./features/step_definitions/tor.rb:512:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:653:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:607:in `/^Tor is ready$/'
features/localization.feature:46:in `And Tor is ready'
features/localization.feature:26:in `And Tor is ready'
Then I successfully start the Unsafe Browser 0.000
And I kill the Unsafe Browser 0.000
When I enable the screen keyboard 0.000
Then the screen keyboard works in Tor Browser 0.000
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "us" 0.000
After features/support/hooks.rb:335 6.148 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#3)' (at time 04:16:52)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/04:16:52_Tails_is_localized_for_every_tier-1_language,_Examples___3_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/04:16:52_Tails_is_localized_for_every_tier-1_language,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/04:16:52_Tails_is_localized_for_every_tier-1_language,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/04:16:52_Tails_is_localized_for_every_tier-1_language,_Examples___3_.journal
After features/support/hooks.rb:105 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
1:9.279
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.006
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 14.076
When I log in to a new session in Russian (ru) 43.345
Then the keyboard layout is set to "ru" 0.135
When the network is plugged 0.074
And Tor is ready 11.647
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/tor.rb:828:in `click_connect_to_tor'
./features/step_definitions/tor.rb:502:in `tca_configure'
./features/step_definitions/tor.rb:512:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:653:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:607:in `/^Tor is ready$/'
features/localization.feature:55:in `And Tor is ready'
features/localization.feature:26:in `And Tor is ready'
Then I successfully start the Unsafe Browser 0.000
And I kill the Unsafe Browser 0.000
When I enable the screen keyboard 0.000
Then the screen keyboard works in Tor Browser 0.000
And DuckDuckGo is the default search engine 0.000
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "ru" 0.000
After features/support/hooks.rb:335 8.178 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#9)' (at time 04:35:33)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/04:35:33_Tails_is_localized_for_every_tier-1_language,_Examples___9_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/04:35:33_Tails_is_localized_for_every_tier-1_language,_Examples___9_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/04:35:33_Tails_is_localized_for_every_tier-1_language,_Examples___9_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/04:35:33_Tails_is_localized_for_every_tier-1_language,_Examples___9_.journal
After features/support/hooks.rb:105 0.000
Feature: Tails persistence
Tags: @product
20.329
Scenario Deleting a Tails persistent partition
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.016
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 12.814
And I log in to a new session without activating the Persistent Storage 7.515
<false> 
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/common_steps.rb:519:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
features/persistence.feature:128:in `And I log in to a new session without activating the Persistent Storage'
Then persistence is disabled 0.000
But a Tails persistence partition exists on USB drive "__internal" 0.000
And all notifications have disappeared 0.000
When I delete the persistent partition 0.000
Then there is no persistence partition on USB drive "__internal" 0.000
After features/support/hooks.rb:335 5.138 
SCENARIO FAILED: 'Deleting a Tails persistent partition' (at time 05:28:18)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/05:28:18_Deleting_a_Tails_persistent_partition.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/05:28:18_Deleting_a_Tails_persistent_partition.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/05:28:18_Deleting_a_Tails_persistent_partition.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/05:28:18_Deleting_a_Tails_persistent_partition.journal
After features/support/hooks.rb:105 0.000
Feature: The Tor enforcement is effective
Tags: @product
2:0.971
Scenario Anti test: Detecting TCP leaks from the Unsafe Browser with the firewall leak detector
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.017
Steps
Given I have started Tails from DVD and logged in and the network is connected 16.035
And I capture all network traffic 0.026
When I successfully start the Unsafe Browser 26.301
And I open the Tails homepage in the Unsafe Browser 18.456
And the Tails homepage loads in the Unsafe Browser 1:0.151
cannot 
cannot find TailsHomepage.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/browser.rb:316:in `/^the Tails homepage loads in the Unsafe Browser$/'
features/tor_enforcement.feature:20:in `And the Tails homepage loads in the Unsafe Browser'
Then the firewall leak detector has detected leaks 0.000
After features/support/hooks.rb:335 6.977 
SCENARIO FAILED: 'Anti test: Detecting TCP leaks from the Unsafe Browser with the firewall leak detector' (at time 06:19:00)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/06:19:00_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/06:19:00_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/06:19:00_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/06:19:00_Anti_test:_Detecting_TCP_leaks_from_the_Unsafe_Browser_with_the_firewall_leak_detector.journal
After features/support/hooks.rb:105 0.060
Feature: Browsing the web using the Tor Browser
Tags: @product
1:58.105
Scenario I can view a file stored in "~/Downloads" but not in ~/.gnupg
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.008
Steps
Given I have started Tails from DVD and logged in and the network is connected 15.982
And I copy "/usr/share/synaptic/html/index.html" to "/home/amnesia/Downloads/synaptic.html" as user "amnesia" 0.408
And I copy "/usr/share/synaptic/html/index.html" to "/home/amnesia/.gnupg/synaptic.html" as user "amnesia" 0.319
And I copy "/usr/share/synaptic/html/index.html" to "/tmp/synaptic.html" as user "amnesia" 0.232
Then the file "/home/amnesia/.gnupg/synaptic.html" exists 0.286
And the file "/lib/live/mount/overlay/rw/home/amnesia/.gnupg/synaptic.html" exists 0.467
And the file "/live/overlay/rw/home/amnesia/.gnupg/synaptic.html" exists 0.246
And the file "/tmp/synaptic.html" exists 0.229
Given I start monitoring the AppArmor log of "torbrowser_firefox" 0.265
When I start the Tor Browser 31.008
And the Tor Browser loads the startup page 5.238
And I open the address "file:///home/amnesia/Downloads/synaptic.html" in the Tor Browser 14.923
Then I see "TorBrowserSynapticManual.png" after at most 5 seconds 0.611
And AppArmor has not denied "torbrowser_firefox" from opening "/home/amnesia/Downloads/synaptic.html" 1.056
When I open the address "file:///home/amnesia/.gnupg/synaptic.html" in the Tor Browser 11.309
Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 0.520
When I open the address "file:///lib/live/mount/overlay/rw/home/amnesia/.gnupg/synaptic.html" in the Tor Browser 6.679
Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 0.531
When I open the address "file:///live/overlay/rw/home/amnesia/.gnupg/synaptic.html" in the Tor Browser 12.310
Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 0.585
When I open the address "file:///tmp/synaptic.html" in the Tor Browser 7.372
Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds 7.518
can 
can still find TorBrowserSynapticManual.png on the screen (FindFailed)
./features/support/helpers/screen.rb:207:in `rescue in wait_vanish'
./features/support/helpers/screen.rb:192:in `wait_vanish'
./features/step_definitions/common_steps.rb:757:in `/^I (do not )?see "([^"]*)" after at most (\d+) seconds$/'
features/torified_browsing.feature:71:in `Then I do not see "TorBrowserSynapticManual.png" after at most 5 seconds'
After features/support/hooks.rb:335 5.601 
SCENARIO FAILED: 'I can view a file stored in "~/Downloads" but not in ~/.gnupg' (at time 06:34:56)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/06:34:56_I_can_view_a_file_stored_in____Downloads__but_not_in___.gnupg.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/06:34:56_I_can_view_a_file_stored_in____Downloads__but_not_in___.gnupg.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/06:34:56_I_can_view_a_file_stored_in____Downloads__but_not_in___.gnupg.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/06:34:56_I_can_view_a_file_stored_in____Downloads__but_not_in___.gnupg.journal
After features/support/hooks.rb:105 0.000
Feature: Browsing the web using the Unsafe Browser
Tags: @product
1:48.387
Scenario The Unsafe Browser can load a web page from the Internet
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.007
Steps
Given I have started Tails from DVD and logged in and the network is connected 12.903
When I successfully start the Unsafe Browser 21.201
When I open the Tails homepage in the Unsafe Browser 13.975
Then the Tails homepage loads in the Unsafe Browser 1:0.306
cannot 
cannot find TailsHomepage.png on the screen (FindFailed)
./features/support/helpers/screen.rb:181:in `rescue in wait'
./features/support/helpers/screen.rb:165:in `wait'
./features/step_definitions/browser.rb:316:in `/^the Tails homepage loads in the Unsafe Browser$/'
features/unsafe_browser.feature:38:in `Then the Tails homepage loads in the Unsafe Browser'
And the Unsafe Browser has sent packets out to the Internet 0.000
After features/support/hooks.rb:335 5.466 
SCENARIO FAILED: 'The Unsafe Browser can load a web page from the Internet' (at time 06:59:41)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/06:59:41_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/06:59:41_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/06:59:41_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/06:59:41_The_Unsafe_Browser_can_load_a_web_page_from_the_Internet.journal
After features/support/hooks.rb:105 0.000
Feature: Using VeraCrypt encrypted volumes
Tags: @product @not_release_blocker
36.716
Scenario Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile
Steps
When I plug and mount a USB drive containing a basic VeraCrypt file container with a keyfile 26.569
And I unlock and mount this VeraCrypt file container with GNOME Disks 10.147
The 
The Dogtail init script raised: ActionNotSupported: Cannot do 'activate' action on [DEAD]
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:346:in `call_tree_node_method'
./features/support/helpers/dogtail.rb:350:in `doActionNamed'
./features/support/helpers/dogtail.rb:364:in `activate'
./features/step_definitions/veracrypt.rb:240:in `/^I unlock and mount this VeraCrypt (volume|file container) with GNOME Disks$/'
features/veracrypt.feature:68:in `And I unlock and mount this VeraCrypt file container with GNOME Disks'
And I open this VeraCrypt volume in GNOME Files 0.000
Then I see the expected contents in this VeraCrypt volume 0.000
When I lock the currently opened VeraCrypt file container 0.000
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:335 6.543 
SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile' (at time 07:10:30)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/07:10:30_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/07:10:30_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/07:10:30_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20297-debug-proxy-refusing-connections/110/artifact/build-artifacts/07:10:30_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.journal
After features/support/hooks.rb:105 0.023