Project Number Date
test_Tails_ISO_21027-fix-interactive-debugging-context 14 29 Jun 2025, 21:00

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 19:48.847 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
45.771
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 11.891
When the network is plugged 33.880
Command 
Command failed (pid 7412 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.039
After features/support/hooks.rb:330 5.763 
SCENARIO FAILED: 'Clock with host's time' (at time 00:13:14)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/14/artifact/build-artifacts/00:13:14_Clock_with_host_s_time_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/14/artifact/build-artifacts/00:13:14_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/14/artifact/build-artifacts/00:13:14_Clock_with_host_s_time.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/14/artifact/build-artifacts/00:13:14_Clock_with_host_s_time.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/14/artifact/build-artifacts/00:13:14_Clock_with_host_s_time.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/14/artifact/build-artifacts/00:13:14_Clock_with_host_s_time.journal
After features/support/hooks.rb:100 0.000
Tags: @product @check_tor_leaks
3:14.670
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.003
Steps
Given I have started Tails from DVD without network and logged in 12.090
When the network is plugged 3:2.580
Command 
Command failed (pid 7561 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.056
After features/support/hooks.rb:330 6.658 
SCENARIO FAILED: 'Clock with host's time while using bridges' (at time 00:16:34)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/14/artifact/build-artifacts/00:16:34_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/14/artifact/build-artifacts/00:16:34_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/14/artifact/build-artifacts/00:16:34_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/14/artifact/build-artifacts/00:16:34_Clock_with_host_s_time_while_using_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/14/artifact/build-artifacts/00:16:34_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/14/artifact/build-artifacts/00:16:34_Clock_with_host_s_time_while_using_bridges.journal
After features/support/hooks.rb:100 0.000
Tags: @product @check_tor_leaks
2:13.692
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 10.946
When I bump the system time with "+1 day" 1.210
And I capture all network traffic 0.008
And the network is plugged 2:1.527
Command 
Command failed (pid 7714 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.056
After features/support/hooks.rb:330 6.172 
SCENARIO FAILED: 'Clock is one day in the future while using obfs4 bridges' (at time 00:18:55)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/14/artifact/build-artifacts/00:18: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_21027-fix-interactive-debugging-context/14/artifact/build-artifacts/00:18: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_21027-fix-interactive-debugging-context/14/artifact/build-artifacts/00:18:55_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/14/artifact/build-artifacts/00:18:55_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/14/artifact/build-artifacts/00:18:55_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/14/artifact/build-artifacts/00:18:55_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.journal
After features/support/hooks.rb:100 0.051
Tags: @product @check_tor_leaks @not_release_blocker
1:43.907
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Before features/support/hooks.rb:509 0.002
Given I have started Tails from DVD without network and logged in 9.210
When I bump the system time with "-15 days" 1.667
And I warm reboot the computer 0.463
And the computer reboots Tails 1:31.663
Then Tails' hardware clock is close to the host system's time 0.902
After features/support/hooks.rb:517 0.147
After features/support/hooks.rb:330 2.232
After features/support/hooks.rb:100 0.006
Tags: @product @check_tor_leaks @not_release_blocker
1:52.588
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Before features/support/hooks.rb:509 0.002
Given I have started Tails from DVD without network and logged in 13.670
When I bump the hardware clock's time with "-15 days" 1.933
And I warm reboot the computer 0.014
And the computer reboots Tails 1:36.014
Then the hardware clock is still off by "-15 days" 0.955
After features/support/hooks.rb:517 0.168
After features/support/hooks.rb:330 0.711
After features/support/hooks.rb:100 0.024
Tags: @product @check_tor_leaks
1:13.856
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.211
And the hardware clock is set to "01 Jan 2000 12:34:56" 0.029
And I start the computer 1.070
And the computer boots Tails 1:12.176
Then the system clock is just past Tails' source date 0.368
After features/support/hooks.rb:517 0.180
After features/support/hooks.rb:330 0.867
After features/support/hooks.rb:100 0.010
Tags: @product @check_tor_leaks
3:18.634
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.005
Steps
Given I have started Tails from DVD without network and logged in 9.954
And I make sure time sync before Tor connects times out 0.629
When the network is plugged 3:8.050
Command 
Command failed (pid 8561 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.042
After features/support/hooks.rb:330 6.170 
SCENARIO FAILED: 'On a clock with host's time, Tor Connection works even if time sync fails' (at time 00:27:15)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/14/artifact/build-artifacts/00:27:15_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/14/artifact/build-artifacts/00:27:15_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/14/artifact/build-artifacts/00:27:15_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/14/artifact/build-artifacts/00:27:15_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/14/artifact/build-artifacts/00:27:15_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/14/artifact/build-artifacts/00:27:15_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
3:53.683
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:509 0.002
Steps
Given I have started Tails from DVD without network and logged in 10.765
When I bump the system time with "+8 hours +15 minutes" 1.911
And all notifications have disappeared 5.407
And I capture all network traffic 0.011
And I make sure time sync before Tor connects fails 0.172
And the network is plugged 3:35.415
Command 
Command failed (pid 8715 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.032
After features/support/hooks.rb:330 5.926 
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:31:15)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/14/artifact/build-artifacts/00:31:15_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/14/artifact/build-artifacts/00:31:15_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/14/artifact/build-artifacts/00:31:15_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/14/artifact/build-artifacts/00:31:15_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/14/artifact/build-artifacts/00:31:15_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/14/artifact/build-artifacts/00:31:15_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.048
Tags: @product @check_tor_leaks
28.133
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.002
Before features/support/hooks.rb:509 0.003
Steps
Given I have started Tails from DVD without network and logged in 11.068
When I bump the system time with "+8 hours +15 minutes" 0.965
And all notifications have disappeared 5.724
And I capture all network traffic 0.013
And the network is plugged 10.360
Command 
Command failed (pid 8871 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.037
After features/support/hooks.rb:330 7.479 
SCENARIO FAILED: 'I can connect to obfs4 bridges having a clock East of UTC while hiding that I am using Tor' (at time 00:31:50)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/14/artifact/build-artifacts/00:31:50_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/14/artifact/build-artifacts/00:31:50_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/14/artifact/build-artifacts/00:31:50_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/14/artifact/build-artifacts/00:31:50_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/14/artifact/build-artifacts/00:31:50_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/14/artifact/build-artifacts/00:31:50_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.059
Tags: @product @check_tor_leaks
1:3.908
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.005
Before features/support/hooks.rb:509 0.009
Steps
Given I have started Tails from DVD without network and logged in 9.315
And I make sure time sync before Tor connects uses a fake connectivity check service 2.559
And the network is plugged 52.033
Command 
Command failed (pid 9027 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.043
After features/support/hooks.rb:330 5.941 
SCENARIO FAILED: 'Time sync before Tor connects sets the same headers as the NetworkManager connectivity check' (at time 00:33:00)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_21027-fix-interactive-debugging-context/14/artifact/build-artifacts/00:33:00_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/14/artifact/build-artifacts/00:33:00_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/14/artifact/build-artifacts/00:33:00_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/14/artifact/build-artifacts/00:33:00_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/14/artifact/build-artifacts/00:33:00_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/14/artifact/build-artifacts/00:33:00_Time_sync_before_Tor_connects_sets_the_same_headers_as_the_NetworkManager_connectivity_check.journal
After features/support/hooks.rb:100 0.000