Project Number Date
test_Tails_ISO_stable 5716 15 Jun 2025, 14:16

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Time syncing 32 8 40 0 0 80 2 8 10 1:6:19.723 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
40.624
Scenario Clock with host's time
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Before features/support/hooks.rb:507 0.006
Steps
Given I have started Tails from DVD without network and logged in 9.133
When the network is plugged 31.491
Command 
Command failed (pid 6884 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_stable/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: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:515 0.050
After features/support/hooks.rb:330 6.844 
SCENARIO FAILED: 'Clock with host's time' (at time 00:13:21)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5716/artifact/build-artifacts/00:13:21_Clock_with_host_s_time_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5716/artifact/build-artifacts/00:13:21_Clock_with_host_s_time.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5716/artifact/build-artifacts/00:13:21_Clock_with_host_s_time.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5716/artifact/build-artifacts/00:13:21_Clock_with_host_s_time.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5716/artifact/build-artifacts/00:13:21_Clock_with_host_s_time.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5716/artifact/build-artifacts/00:13:21_Clock_with_host_s_time.journal
After features/support/hooks.rb:100 0.000
Tags: @product @check_tor_leaks
10:10.327
Scenario Clock with host's time while using bridges
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Before features/support/hooks.rb:507 0.003
Steps
Given I have started Tails from DVD without network and logged in 8.476
When the network is plugged 10:1.851
Command 
Command failed (pid 7034 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_stable/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:    0, 004ba                    , desc                          , Not in dir file
test021bridge:  100, 004ba                    , desc                          , Dir info cached
test022obfs4 :  100, 004ba                    , desc                          , Dir info cached
test023obfs4 :  100, 004ba                    , desc                          , Dir info cached
test024defbr :  100, 004ba                    , desc                          , Dir info cached

 (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:515 0.042
After features/support/hooks.rb:330 7.084 
SCENARIO FAILED: 'Clock with host's time while using bridges' (at time 00:23:38)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5716/artifact/build-artifacts/00:23:38_Clock_with_host_s_time_while_using_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5716/artifact/build-artifacts/00:23:38_Clock_with_host_s_time_while_using_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5716/artifact/build-artifacts/00:23:38_Clock_with_host_s_time_while_using_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5716/artifact/build-artifacts/00:23:38_Clock_with_host_s_time_while_using_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5716/artifact/build-artifacts/00:23:38_Clock_with_host_s_time_while_using_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5716/artifact/build-artifacts/00:23:38_Clock_with_host_s_time_while_using_bridges.journal
After features/support/hooks.rb:100 0.000
Tags: @product @check_tor_leaks
10:10.199
Scenario Clock is one day in the future while using obfs4 bridges
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Before features/support/hooks.rb:507 0.006
Steps
Given I have started Tails from DVD without network and logged in 9.203
When I bump the system time with "+1 day" 0.372
And I capture all network traffic 0.003
And the network is plugged 10:0.620
Command 
Command failed (pid 7285 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_stable/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:    0, 004ba                    , desc                          , Not in dir file
test021bridge:  100, 004ba                    , desc                          , Dir info cached
test022obfs4 :  100, 004ba                    , desc                          , Dir info cached
test023obfs4 :  100, 004ba                    , desc                          , Dir info cached
test024defbr :  100, 004ba                    , desc                          , Dir info cached

 (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:515 0.036
After features/support/hooks.rb:330 7.607 
SCENARIO FAILED: 'Clock is one day in the future while using obfs4 bridges' (at time 00:33:55)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5716/artifact/build-artifacts/00:33:55_Clock_is_one_day_in_the_future_while_using_obfs4_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5716/artifact/build-artifacts/00:33:55_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_stable/5716/artifact/build-artifacts/00:33:55_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5716/artifact/build-artifacts/00:33:55_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5716/artifact/build-artifacts/00:33:55_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5716/artifact/build-artifacts/00:33:55_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.journal
After features/support/hooks.rb:100 0.038
Tags: @product @check_tor_leaks @not_release_blocker
1:43.398
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Before features/support/hooks.rb:507 0.004
Given I have started Tails from DVD without network and logged in 10.023
When I bump the system time with "-15 days" 0.362
And I warm reboot the computer 0.015
And the computer reboots Tails 1:32.673
Then Tails' hardware clock is close to the host system's time 0.323
After features/support/hooks.rb:515 0.248
After features/support/hooks.rb:330 0.765
After features/support/hooks.rb:100 0.026
Tags: @product @check_tor_leaks @not_release_blocker
1:37.840
Scenario Anti-test: Changes to the hardware clock are kept when rebooting
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.013
Before features/support/hooks.rb:507 0.016
Steps
Given I have started Tails from DVD without network and logged in 9.594
When I bump the hardware clock's time with "-15 days" 3.307
And I warm reboot the computer 0.045
And the computer reboots Tails 1:24.715
Then the hardware clock is still off by "-15 days" 0.177
The 
The hardware clock of the Tails VM should be between '2025-05-31 08:27:34 +0000' and '2025-05-31 08:27:50 +0000', but is actually '2025-05-31 08:27:50 +0000'.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/time_syncing.rb:161:in `/^the hardware clock is still off by "([^"]+)"$/'
features/time_syncing.feature:46:in `Then the hardware clock is still off by "-15 days"'
After features/support/hooks.rb:515 0.053
After features/support/hooks.rb:330 4.919 
SCENARIO FAILED: 'Anti-test: Changes to the hardware clock are kept when rebooting' (at time 00:37:25)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5716/artifact/build-artifacts/00:37:25_Anti-test:_Changes_to_the_hardware_clock_are_kept_when_rebooting.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5716/artifact/build-artifacts/00:37:25_Anti-test:_Changes_to_the_hardware_clock_are_kept_when_rebooting.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5716/artifact/build-artifacts/00:37:25_Anti-test:_Changes_to_the_hardware_clock_are_kept_when_rebooting.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5716/artifact/build-artifacts/00:37:25_Anti-test:_Changes_to_the_hardware_clock_are_kept_when_rebooting.journal
After features/support/hooks.rb:100 0.006
Tags: @product @check_tor_leaks
1:2.132
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Before features/support/hooks.rb:507 0.002
Given a computer 0.156
And the hardware clock is set to "01 Jan 2000 12:34:56" 0.037
And I start the computer 1.228
And the computer boots Tails 1:0.611
Then the system clock is just past Tails' source date 0.098
After features/support/hooks.rb:515 0.115
After features/support/hooks.rb:330 0.765
After features/support/hooks.rb:100 0.005
Tags: @product @check_tor_leaks
10:12.873
Scenario On a clock with host's time, Tor Connection works even if time sync fails
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Before features/support/hooks.rb:507 0.003
Steps
Given I have started Tails from DVD without network and logged in 10.545
And I make sure time sync before Tor connects times out 1.187
When the network is plugged 10:1.139
Command 
Command failed (pid 8129 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/chutney/test-network", {:err=>[:child, :out]}]
Bootstrap failed: 601 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:    0, 004ba                    , desc                          , Not in dir file
test021bridge:  100, 004ba                    , desc                          , Dir info cached
test022obfs4 :  100, 004ba                    , desc                          , Dir info cached
test023obfs4 :  100, 004ba                    , desc                          , Dir info cached
test024defbr :  100, 004ba                    , desc                          , Dir info cached

 (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:515 0.068
After features/support/hooks.rb:330 6.340 
SCENARIO FAILED: 'On a clock with host's time, Tor Connection works even if time sync fails' (at time 00:48:46)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5716/artifact/build-artifacts/00:48:46_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_stable/5716/artifact/build-artifacts/00:48:46_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_stable/5716/artifact/build-artifacts/00:48:46_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_stable/5716/artifact/build-artifacts/00:48:46_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_stable/5716/artifact/build-artifacts/00:48:46_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_stable/5716/artifact/build-artifacts/00:48:46_On_a_clock_with_host_s_time,_Tor_Connection_works_even_if_time_sync_fails.journal
After features/support/hooks.rb:100 0.000
Tags: @product @check_tor_leaks
10:17.016
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:266 0.000
Before features/support/hooks.rb:273 0.002
Before features/support/hooks.rb:507 0.002
Steps
Given I have started Tails from DVD without network and logged in 10.965
When I bump the system time with "+8 hours +15 minutes" 0.293
And all notifications have disappeared 4.466
And I capture all network traffic 0.003
And I make sure time sync before Tor connects fails 0.103
And the network is plugged 10:1.184
Command 
Command failed (pid 8396 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/chutney/test-network", {:err=>[:child, :out]}]
Bootstrap failed: 601 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:    0, 004ba                    , desc                          , Not in dir file
test021bridge:  100, 004ba                    , desc                          , Dir info cached
test022obfs4 :  100, 004ba                    , desc                          , Dir info cached
test023obfs4 :  100, 004ba                    , desc                          , Dir info cached
test024defbr :  100, 004ba                    , desc                          , Dir info cached

 (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:515 0.032
After features/support/hooks.rb:330 7.143 
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:59:10)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5716/artifact/build-artifacts/00:59:10_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_stable/5716/artifact/build-artifacts/00:59:10_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_stable/5716/artifact/build-artifacts/00:59:10_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_stable/5716/artifact/build-artifacts/00:59:10_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_stable/5716/artifact/build-artifacts/00:59:10_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_stable/5716/artifact/build-artifacts/00:59:10_I_can_manually_recover_from_time_sync_failure_when_connecting_automatically_to_obfs4_bridges_with_a_clock_East_of_UTC.journal
After features/support/hooks.rb:100 0.051
Tags: @product @check_tor_leaks
10:14.430
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:266 0.000
Before features/support/hooks.rb:273 0.028
Before features/support/hooks.rb:507 0.011
Steps
Given I have started Tails from DVD without network and logged in 9.648
When I bump the system time with "+8 hours +15 minutes" 0.189
And all notifications have disappeared 4.150
And I capture all network traffic 0.003
And the network is plugged 10:0.439
Command 
Command failed (pid 8563 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_stable/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:    0, 004ba                    , desc                          , Not in dir file
test021bridge:  100, 004ba                    , desc                          , Dir info cached
test022obfs4 :  100, 004ba                    , desc                          , Dir info cached
test023obfs4 :  100, 004ba                    , desc                          , Dir info cached
test024defbr :  100, 004ba                    , desc                          , Dir info cached

 (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:515 0.045
After features/support/hooks.rb:330 6.836 
SCENARIO FAILED: 'I can connect to obfs4 bridges having a clock East of UTC while hiding that I am using Tor' (at time 01:09:31)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5716/artifact/build-artifacts/01:09:31_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_stable/5716/artifact/build-artifacts/01:09:31_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_stable/5716/artifact/build-artifacts/01:09:31_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_stable/5716/artifact/build-artifacts/01:09:31_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_stable/5716/artifact/build-artifacts/01:09:31_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_stable/5716/artifact/build-artifacts/01:09:31_I_can_connect_to_obfs4_bridges_having_a_clock_East_of_UTC_while_hiding_that_I_am_using_Tor.journal
After features/support/hooks.rb:100 0.029
Tags: @product @check_tor_leaks
10:10.879
Scenario Time sync before Tor connects sets the same headers as the NetworkManager connectivity check
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Before features/support/hooks.rb:507 0.004
Steps
Given I have started Tails from DVD without network and logged in 9.480
And I make sure time sync before Tor connects uses a fake connectivity check service 1.163
And the network is plugged 10:0.236
Command 
Command failed (pid 8729 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_stable/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:    0, 004ba                    , desc                          , Not in dir file
test021bridge:  100, 004ba                    , desc                          , Dir info cached
test022obfs4 :  100, 004ba                    , desc                          , Dir info cached
test023obfs4 :  100, 004ba                    , desc                          , Dir info cached
test024defbr :  100, 004ba                    , desc                          , Dir info cached

 (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:515 0.025
After features/support/hooks.rb:330 6.584 
SCENARIO FAILED: 'Time sync before Tor connects sets the same headers as the NetworkManager connectivity check' (at time 01:19:49)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5716/artifact/build-artifacts/01:19:49_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_stable/5716/artifact/build-artifacts/01:19:49_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_stable/5716/artifact/build-artifacts/01:19:49_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_stable/5716/artifact/build-artifacts/01:19:49_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_stable/5716/artifact/build-artifacts/01:19:49_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_stable/5716/artifact/build-artifacts/01:19:49_Time_sync_before_Tor_connects_sets_the_same_headers_as_the_NetworkManager_connectivity_check.journal
After features/support/hooks.rb:100 0.002