Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 73 15 May 2024, 06:43

Failures Overview

The following summary displays scenarios that failed.

Feature: Time syncing
Tags: @product @check_tor_leaks
19.200
Scenario On a clock with host's time, Tor Connection works even if time sync fails
Before features/support/hooks.rb:259 0.002
Before features/support/hooks.rb:456 0.002
Steps
Given I have started Tails from DVD without network and logged in 8.307
And I make sure time sync before Tor connects times out 1.235
When the network is plugged 0.038
And I successfully configure Tor 9.618
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:146:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:52:in `try_for'
./features/step_definitions/tor.rb:811:in `click_connect_to_tor'
./features/step_definitions/tor.rb:483:in `tca_configure'
./features/step_definitions/tor.rb:493:in `/^I configure a direct connection in the Tor Connection Assistant$/'
./features/step_definitions/common_steps.rb:645:in `/^I successfully configure Tor$/'
features/time_syncing.feature:59:in `And I successfully configure Tor'
Then the system clock is less than 5 minutes incorrect 0.000
After features/support/hooks.rb:464 0.050
After features/support/hooks.rb:305 4.012 
SCENARIO FAILED: 'On a clock with host's time, Tor Connection works even if time sync fails' (at time 00:16:53)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/73/artifact/build-artifacts/00:16:53_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_20268-more-early-patch-functionality/73/artifact/build-artifacts/00:16:53_On_a_clock_with_host_s_time,_Tor_Connection_works_even_if_time_sync_fails.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/73/artifact/build-artifacts/00:16:53_On_a_clock_with_host_s_time,_Tor_Connection_works_even_if_time_sync_fails.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/73/artifact/build-artifacts/00:16:53_On_a_clock_with_host_s_time,_Tor_Connection_works_even_if_time_sync_fails.journal
After features/support/hooks.rb:89 0.001
Feature: Tails-related cryptographic keys are up-to-date
Tags: @product
23.875
Scenario The included APT repository keys are up-to-date
Before features/support/hooks.rb:259 0.008
Steps
Given I have started Tails from DVD without network and logged in 8.619
Then the keys trusted by APT are valid for the next 3 months 15.255
The 
The following APT key(s) will not be valid in 3 months: A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89, 2265EB4CB2BF88D900AE8D1B74A941BA219EC810.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/checks.rb:29:in `assert_all_keys_are_valid_for_n_months'
./features/step_definitions/checks.rb:8:in `/^the keys trusted by APT are valid for the next (\d+) months$/'
features/keys.feature:11:in `Then the keys trusted by APT are valid for the next 3 months'
After features/support/hooks.rb:305 4.502 
SCENARIO FAILED: 'The included APT repository keys are up-to-date' (at time 02:20:50)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/73/artifact/build-artifacts/02:20:50_The_included_APT_repository_keys_are_up-to-date.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/73/artifact/build-artifacts/02:20:50_The_included_APT_repository_keys_are_up-to-date.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/73/artifact/build-artifacts/02:20:50_The_included_APT_repository_keys_are_up-to-date.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/73/artifact/build-artifacts/02:20:50_The_included_APT_repository_keys_are_up-to-date.journal
After features/support/hooks.rb:89 0.000