Project Number Date
test_Tails_ISO_20531-early-reporting-of-bad-devices 26 18 Dec 2024, 04:11

Failures Overview

The following summary displays scenarios that failed.

Feature: Time syncing
51.533
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:269 0.002
Before features/support/hooks.rb:507 0.002
Steps
Given I have started Tails from DVD without network and logged in 8.415
When I bump the system time with "+8 hours +15 minutes" 0.288
And all notifications have disappeared 3.840
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 0.072
And the Tor Connection Assistant autostarts 3.860
When I configure the default bridges in the Tor Connection Assistant in easy mode without connecting 5.031
And I click "Connect to Tor" 1.168
And the Tor Connection Assistant fails to connect to Tor 15.782
# The "Fix Clock" button allows users to recover from this bug
Then I set the time zone in Tor Connection to "Asia/Shanghai" 12.966
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/tor.rb:865:in `/^I set the time zone in Tor Connection to "([^"]*)"$/'
features/time_syncing.feature:74:in `Then I set the time zone in Tor Connection to "Asia/Shanghai"'
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.037
After features/support/hooks.rb:326 5.008

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:17:19)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20531-early-reporting-of-bad-devices/26/artifact/build-artifacts/00:17:19_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_20531-early-reporting-of-bad-devices/26/artifact/build-artifacts/00:17:19_I_can_manually_recover_from_time_sync_failure_when_connecting_automatically_to_obfs4_bridges_with_a_clock_East_of_UTC.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20531-early-reporting-of-bad-devices/26/artifact/build-artifacts/00:17:19_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_20531-early-reporting-of-bad-devices/26/artifact/build-artifacts/00:17:19_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.033