Project Number Date
test_Tails_ISO_21027-fix-interactive-debugging-context 10 25 Jun 2025, 21: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 13:50.631 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
1:8.505
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.004
Steps
Given I have started Tails from DVD without network and logged in 14.215
When the network is plugged 54.290
Command 
Command failed (pid 8549 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/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.046
After features/support/hooks.rb:330 6.134 
SCENARIO FAILED: 'Clock with host's time' (at time 00:13:52)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:13:52_Clock_with_host_s_time_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:13:52_Clock_with_host_s_time.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:13:52_Clock_with_host_s_time.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:13:52_Clock_with_host_s_time.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:13:52_Clock_with_host_s_time.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:13:52_Clock_with_host_s_time.journal
After features/support/hooks.rb:100 0.000
Tags: @product @check_tor_leaks
34.263
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:509 0.002
Steps
Given I have started Tails from DVD without network and logged in 12.166
When the network is plugged 22.097
Command 
Command failed (pid 8702 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/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.040
After features/support/hooks.rb:330 6.534 
SCENARIO FAILED: 'Clock with host's time while using bridges' (at time 00:14:33)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:14:33_Clock_with_host_s_time_while_using_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:14:33_Clock_with_host_s_time_while_using_bridges.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:14:33_Clock_with_host_s_time_while_using_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:14:33_Clock_with_host_s_time_while_using_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:14:33_Clock_with_host_s_time_while_using_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:14:33_Clock_with_host_s_time_while_using_bridges.journal
After features/support/hooks.rb:100 0.000
Tags: @product @check_tor_leaks
35.851
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.003
Before features/support/hooks.rb:509 0.003
Steps
Given I have started Tails from DVD without network and logged in 13.309
When I bump the system time with "+1 day" 0.387
And I capture all network traffic 0.007
And the network is plugged 22.147
Command 
Command failed (pid 8857 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/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.038
After features/support/hooks.rb:330 6.106 
SCENARIO FAILED: 'Clock is one day in the future while using obfs4 bridges' (at time 00:15:15)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:15:15_Clock_is_one_day_in_the_future_while_using_obfs4_bridges_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:15:15_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_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:15:15_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:15:15_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:15:15_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:15:15_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.journal
After features/support/hooks.rb:100 0.055
Tags: @product @check_tor_leaks @not_release_blocker
1:52.963
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Before features/support/hooks.rb:509 0.003
Given I have started Tails from DVD without network and logged in 9.727
When I bump the system time with "-15 days" 0.420
And I warm reboot the computer 0.015
And the computer reboots Tails 1:42.575
Then Tails' hardware clock is close to the host system's time 0.224
After features/support/hooks.rb:517 0.180
After features/support/hooks.rb:330 1.096
After features/support/hooks.rb:100 0.039
Tags: @product @check_tor_leaks @not_release_blocker
1:45.640
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Before features/support/hooks.rb:509 0.005
Given I have started Tails from DVD without network and logged in 9.728
When I bump the hardware clock's time with "-15 days" 3.018
And I warm reboot the computer 0.065
And the computer reboots Tails 1:31.987
Then the hardware clock is still off by "-15 days" 0.841
After features/support/hooks.rb:517 0.135
After features/support/hooks.rb:330 1.140
After features/support/hooks.rb:100 0.007
Tags: @product @check_tor_leaks
1:12.230
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 a computer 0.314
And the hardware clock is set to "01 Jan 2000 12:34:56" 0.036
And I start the computer 1.450
And the computer boots Tails 1:10.177
Then the system clock is just past Tails' source date 0.251
After features/support/hooks.rb:517 0.188
After features/support/hooks.rb:330 0.837
After features/support/hooks.rb:100 0.008
Tags: @product @check_tor_leaks
2:37.482
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.003
Before features/support/hooks.rb:509 0.003
Steps
Given I have started Tails from DVD without network and logged in 9.807
And I make sure time sync before Tor connects times out 1.775
When the network is plugged 2:25.898
Command 
Command failed (pid 9714 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/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:517 0.046
After features/support/hooks.rb:330 6.010 
SCENARIO FAILED: 'On a clock with host's time, Tor Connection works even if time sync fails' (at time 00:22:54)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:22:54_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_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:22:54_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_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:22:54_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_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:22:54_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_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:22:54_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_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:22:54_On_a_clock_with_host_s_time,_Tor_Connection_works_even_if_time_sync_fails.journal
After features/support/hooks.rb:100 0.001
Tags: @product @check_tor_leaks
1:35.360
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.003
Before features/support/hooks.rb:509 0.002
Steps
Given I have started Tails from DVD without network and logged in 10.877
When I bump the system time with "+8 hours +15 minutes" 0.377
And all notifications have disappeared 5.173
And I capture all network traffic 0.002
And I make sure time sync before Tor connects fails 0.202
And the network is plugged 1:18.727
Command 
Command failed (pid 9867 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/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.035
After features/support/hooks.rb:330 6.301 
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:24:35)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:24: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_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:24: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_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:24: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_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:24: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_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:24: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_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:24: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:100 0.051
Tags: @product @check_tor_leaks
48.714
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.036
Before features/support/hooks.rb:509 0.024
Steps
Given I have started Tails from DVD without network and logged in 10.453
When I bump the system time with "+8 hours +15 minutes" 0.222
And all notifications have disappeared 5.277
And I capture all network traffic 0.005
And the network is plugged 32.756
Command 
Command failed (pid 10026 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/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.038
After features/support/hooks.rb:330 6.376 
SCENARIO FAILED: 'I can connect to obfs4 bridges having a clock East of UTC while hiding that I am using Tor' (at time 00:25:30)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:25:30_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_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:25:30_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_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:25:30_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_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:25:30_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_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:25:30_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_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:25:30_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.063
Tags: @product @check_tor_leaks
1:39.618
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.003
Steps
Given I have started Tails from DVD without network and logged in 9.977
And I make sure time sync before Tor connects uses a fake connectivity check service 2.148
And the network is plugged 1:27.492
Command 
Command failed (pid 10181 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/features/scripts/chutney", "wait_for_bootstrap", "/var/lib/jenkins/workspace/test_Tails_ISO_21027-fix-interactive-debugging-context/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.041
After features/support/hooks.rb:330 6.370 
SCENARIO FAILED: 'Time sync before Tor connects sets the same headers as the NetworkManager connectivity check' (at time 00:27:16)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:27:16_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_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:27:16_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_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:27:16_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_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:27:16_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_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:27:16_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_21027-fix-interactive-debugging-context/10/artifact/build-artifacts/00:27:16_Time_sync_before_Tor_connects_sets_the_same_headers_as_the_NetworkManager_connectivity_check.journal
After features/support/hooks.rb:100 0.001