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

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Time syncing 33 7 40 0 0 80 3 7 10 45:53.991 Failed
Tags: @product @check_tor_leaks
Feature Time syncing
As a Tails user I want Tor to work properly And for that I need a reasonably accurate system clock
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
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
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
Tags: @product @check_tor_leaks @not_release_blocker
1:40.801
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.003
Before features/support/hooks.rb:512 0.003
Given I have started Tails from DVD without network and logged in 11.006
When I bump the system time with "-15 days" 0.513
And I warm reboot the computer 0.069
And the computer reboots Tails 1:28.956
Then Tails' hardware clock is close to the host system's time 0.255
After features/support/hooks.rb:520 0.123
After features/support/hooks.rb:335 2.738
After features/support/hooks.rb:105 0.052
Tags: @product @check_tor_leaks @not_release_blocker
1:44.053
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.022
Before features/support/hooks.rb:512 0.011
Given I have started Tails from DVD without network and logged in 9.795
When I bump the hardware clock's time with "-15 days" 1.241
And I warm reboot the computer 0.012
And the computer reboots Tails 1:32.282
Then the hardware clock is still off by "-15 days" 0.721
After features/support/hooks.rb:520 0.249
After features/support/hooks.rb:335 0.825
After features/support/hooks.rb:105 0.006
Tags: @product @check_tor_leaks
1:7.798
Before features/support/hooks.rb:271 0.000
Before features/support/hooks.rb:278 0.003
Before features/support/hooks.rb:512 0.002
Given a computer 0.163
And the hardware clock is set to "01 Jan 2000 12:34:56" 0.025
And I start the computer 1.228
And the computer boots Tails 1:6.047
Then the system clock is just past Tails' source date 0.334
After features/support/hooks.rb:520 0.180
After features/support/hooks.rb:335 0.867
After features/support/hooks.rb:105 0.006
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
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
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
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