Project Number Date
test_Tails_ISO_improve-cmd-logging 3 17 Jul 2025, 16:58

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Time syncing 26 8 46 0 0 80 2 8 10 14:59.171 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
32.922
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:509 0.003
Steps
Given I have started Tails from DVD without network and logged in 20.718
When the network is plugged 12.203
Command 
Command failed (pid 5857 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/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:517 0.047
After features/support/hooks.rb:330 7.669 
SCENARIO FAILED: 'Clock with host's time' (at time 00:21:19)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:21:19_Clock_with_host_s_time_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:21:19_Clock_with_host_s_time.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:21:19_Clock_with_host_s_time.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:21:19_Clock_with_host_s_time.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:21:19_Clock_with_host_s_time.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:21:19_Clock_with_host_s_time.journal
After features/support/hooks.rb:100 0.000
Tags: @product @check_tor_leaks
1:38.581
Scenario Clock with host's time while using bridges
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Before features/support/hooks.rb:509 0.002
Steps
Given I have started Tails from DVD without network and logged in 1:22.583
When the network is plugged 15.997
Command 
Command failed (pid 6352 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/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: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:517 0.036
After features/support/hooks.rb:330 15.199 
SCENARIO FAILED: 'Clock with host's time while using bridges' (at time 00:23:09)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:23:09_Clock_with_host_s_time_while_using_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:23:09_Clock_with_host_s_time_while_using_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:23:09_Clock_with_host_s_time_while_using_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:23:09_Clock_with_host_s_time_while_using_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:23:09_Clock_with_host_s_time_while_using_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:23:09_Clock_with_host_s_time_while_using_bridges.journal
After features/support/hooks.rb:100 0.000
Tags: @product @check_tor_leaks
1:18.465
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.005
Before features/support/hooks.rb:509 0.004
Steps
Given I have started Tails from DVD without network and logged in 48.698
When I bump the system time with "+1 day" 5.502
And I capture all network traffic 0.110
And the network is plugged 24.154
Command 
Command failed (pid 6732 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/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: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:517 0.041
After features/support/hooks.rb:330 6.635 
SCENARIO FAILED: 'Clock is one day in the future while using obfs4 bridges' (at time 00:24:39)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:24:39_Clock_is_one_day_in_the_future_while_using_obfs4_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:24:39_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_improve-cmd-logging/3/artifact/build-artifacts/00:24:39_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:24:39_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:24:39_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:24:39_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.journal
After features/support/hooks.rb:100 0.048
Tags: @product @check_tor_leaks @not_release_blocker
2:45.659
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Before features/support/hooks.rb:509 0.003
Given I have started Tails from DVD without network and logged in 20.765
When I bump the system time with "-15 days" 0.650
And I warm reboot the computer 0.234
And the computer reboots Tails 2:22.954
Then Tails' hardware clock is close to the host system's time 1.054
After features/support/hooks.rb:517 4.692
After features/support/hooks.rb:330 3.059
After features/support/hooks.rb:100 0.018
Tags: @product @check_tor_leaks @not_release_blocker
1:12.875
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.009
Before features/support/hooks.rb:509 0.013
Steps
Given I have started Tails from DVD without network and logged in 1:12.875
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ without\ network\ and\ logged\ in$/'
features/time_syncing.feature:42:in `Given I have started Tails from DVD without network and logged in'
When I bump the hardware clock's time with "-15 days" 0.000
And I warm reboot the computer 0.000
And the computer reboots Tails 0.000
Then the hardware clock is still off by "-15 days" 0.000
After features/support/hooks.rb:517 0.042
After features/support/hooks.rb:330 8.201 
SCENARIO FAILED: 'Anti-test: Changes to the hardware clock are kept when rebooting' (at time 00:28:55)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:28:55_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_improve-cmd-logging/3/artifact/build-artifacts/00:28:55_Anti-test:_Changes_to_the_hardware_clock_are_kept_when_rebooting.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:28:55_Anti-test:_Changes_to_the_hardware_clock_are_kept_when_rebooting.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:28:55_Anti-test:_Changes_to_the_hardware_clock_are_kept_when_rebooting.journal
After features/support/hooks.rb:100 0.000
Tags: @product @check_tor_leaks
2:0.657
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Before features/support/hooks.rb:509 0.004
Given a computer 0.270
And the hardware clock is set to "01 Jan 2000 12:34:56" 0.044
And I start the computer 1.448
And the computer boots Tails 1:58.704
Then the system clock is just past Tails' source date 0.188
After features/support/hooks.rb:517 0.113
After features/support/hooks.rb:330 0.861
After features/support/hooks.rb:100 0.031
Tags: @product @check_tor_leaks
1:11.733
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.006
Before features/support/hooks.rb:509 0.004
Steps
Given I have started Tails from DVD without network and logged in 1:11.733
Failed 
Failed to restore snapshot (RuntimeError)
./features/step_definitions/common_steps.rb:89:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/common_steps.rb:95:in `rescue in post_snapshot_restore_hook'
./features/step_definitions/common_steps.rb:72:in `post_snapshot_restore_hook'
./features/step_definitions/snapshots.rb:167:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ from\ DVD\ without\ network\ and\ logged\ in$/'
features/time_syncing.feature:56:in `Given I have started Tails from DVD without network and logged in'
And I make sure time sync before Tor connects times out 0.000
When the network is plugged 0.000
And I successfully configure Tor 0.000
Then the system clock is less than 5 minutes incorrect 0.000
After features/support/hooks.rb:517 0.036
After features/support/hooks.rb:330 6.950 
SCENARIO FAILED: 'On a clock with host's time, Tor Connection works even if time sync fails' (at time 00:32:16)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:32:16_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_improve-cmd-logging/3/artifact/build-artifacts/00:32:16_On_a_clock_with_host_s_time,_Tor_Connection_works_even_if_time_sync_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:32:16_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_improve-cmd-logging/3/artifact/build-artifacts/00:32:16_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
1:36.073
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.004
Before features/support/hooks.rb:509 0.004
Steps
Given I have started Tails from DVD without network and logged in 1:8.851
When I bump the system time with "+8 hours +15 minutes" 2.667
And all notifications have disappeared 9.284
And I capture all network traffic 0.018
And I make sure time sync before Tor connects fails 0.257
And the network is plugged 14.994
Command 
Command failed (pid 8895 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/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:517 0.040
After features/support/hooks.rb:330 6.399 
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:33:58)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:33:58_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_improve-cmd-logging/3/artifact/build-artifacts/00:33:58_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_improve-cmd-logging/3/artifact/build-artifacts/00:33:58_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_improve-cmd-logging/3/artifact/build-artifacts/00:33:58_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_improve-cmd-logging/3/artifact/build-artifacts/00:33:58_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_improve-cmd-logging/3/artifact/build-artifacts/00:33:58_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.054
Tags: @product @check_tor_leaks
48.035
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.010
Before features/support/hooks.rb:509 0.013
Steps
Given I have started Tails from DVD without network and logged in 21.805
When I bump the system time with "+8 hours +15 minutes" 0.228
And all notifications have disappeared 13.549
And I capture all network traffic 0.003
And the network is plugged 12.448
Command 
Command failed (pid 9065 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/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:517 0.039
After features/support/hooks.rb:330 8.515 
SCENARIO FAILED: 'I can connect to obfs4 bridges having a clock East of UTC while hiding that I am using Tor' (at time 00:34:54)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:34:54_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_improve-cmd-logging/3/artifact/build-artifacts/00:34:54_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_improve-cmd-logging/3/artifact/build-artifacts/00:34:54_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_improve-cmd-logging/3/artifact/build-artifacts/00:34:54_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_improve-cmd-logging/3/artifact/build-artifacts/00:34:54_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_improve-cmd-logging/3/artifact/build-artifacts/00:34:54_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.034
Tags: @product @check_tor_leaks
1:54.165
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.002
Before features/support/hooks.rb:509 0.004
Steps
Given I have started Tails from DVD without network and logged in 56.073
And I make sure time sync before Tor connects uses a fake connectivity check service 1.483
And the network is plugged 56.609
Command 
Command failed (pid 9454 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_improve-cmd-logging/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:517 0.043
After features/support/hooks.rb:330 6.021 
SCENARIO FAILED: 'Time sync before Tor connects sets the same headers as the NetworkManager connectivity check' (at time 00:36:56)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_improve-cmd-logging/3/artifact/build-artifacts/00:36:56_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_improve-cmd-logging/3/artifact/build-artifacts/00:36:56_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_improve-cmd-logging/3/artifact/build-artifacts/00:36:56_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_improve-cmd-logging/3/artifact/build-artifacts/00:36:56_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_improve-cmd-logging/3/artifact/build-artifacts/00:36:56_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_improve-cmd-logging/3/artifact/build-artifacts/00:36:56_Time_sync_before_Tor_connects_sets_the_same_headers_as_the_NetworkManager_connectivity_check.journal
After features/support/hooks.rb:100 0.000