Project Number Date
test_Tails_ISO_stable 4857 28 May 2024, 16:39

Failures Overview

The following summary displays scenarios that failed.

Feature: Time syncing
Tags: @product @check_tor_leaks
47.735
Scenario Clock is one day in the future while using obfs4 bridges
Before features/support/hooks.rb:259 0.004
Before features/support/hooks.rb:456 0.005
Steps
Given I have started Tails from DVD without network and logged in 8.580
When I bump the system time with "+1 day" 0.379
And I capture all network traffic 0.003
And the network is plugged 0.056
And the Tor Connection Assistant autostarts 4.681
And I configure some obfs4 bridges in the Tor Connection Assistant in easy mode 34.034
TCA 
TCA failed to connect to Tor (TCAConnectionFailure)
./features/step_definitions/tor.rb:418:in `/^the Tor Connection Assistant connects to Tor$/'
./features/step_definitions/tor.rb:484:in `tca_configure'
./features/step_definitions/tor.rb:611:in `/^I configure (?:some|the) (persistent )?(\w+) bridges (from a QR code )?in the Tor Connection Assistant(?: in (easy|hide) mode)?( without connecting|)$/'
features/time_syncing.feature:27:in `And I configure some obfs4 bridges in the Tor Connection Assistant in easy mode'
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:464 0.044
After features/support/hooks.rb:305 4.629 
SCENARIO FAILED: 'Clock is one day in the future while using obfs4 bridges' (at time 00:13:22)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4857/artifact/build-artifacts/00:13:22_Clock_is_one_day_in_the_future_while_using_obfs4_bridges_chutney-data
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4857/artifact/build-artifacts/00:13:22_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4857/artifact/build-artifacts/00:13:22_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4857/artifact/build-artifacts/00:13:22_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4857/artifact/build-artifacts/00:13:22_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.boot-log
Obfs4proxy logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4857/artifact/build-artifacts/00:13:22_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.obfs4proxy
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4857/artifact/build-artifacts/00:13:22_Clock_is_one_day_in_the_future_while_using_obfs4_bridges.journal
After features/support/hooks.rb:89 0.040
Feature: Installing Tails to a USB drive
Tags: @product
1:59.488
Scenario The system partition is updated when booting from a USB drive where a Tails USB image was copied
Before features/support/hooks.rb:259 0.002
Steps
Given a computer 0.162
And I start Tails from USB drive "usbimage" with network unplugged and I login 1:59.326
try_for() 
try_for() timeout expired
Last ignored exception was: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/tmp/gdm-env'
./features/support/helpers/remote_shell.rb:71:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:42:in `loop'
./features/support/helpers/remote_shell.rb:42:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb:174:in `execute'
./features/support/helpers/remote_shell.rb:185:in `initialize'
./features/support/helpers/dogtail.rb:80:in `new'
./features/support/helpers/dogtail.rb:80:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/usb.rb:108:in `new'
./features/step_definitions/usb.rb:108:in `greeter'
./features/step_definitions/common_steps.rb:448:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:79:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:67:in `loop'
./features/support/helpers/misc_helpers.rb:67:in `block in try_for'
./features/support/helpers/misc_helpers.rb:66:in `try_for'
./features/step_definitions/common_steps.rb:447:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:286:in `block in <top (required)>' (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/common_steps.rb:447:in `/^the computer (?:re)?boots Tails( with genuine APT sources)?$/'
./features/step_definitions/common_steps.rb:286:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/usb_install.feature:100:in `And I start Tails from USB drive "usbimage" with network unplugged and I login'
Then Tails is running from USB drive "usbimage" 0.000
And the label of the system partition on "usbimage" is "Tails" 0.000
And the system partition on "usbimage" is an EFI system partition 0.000
And the FAT filesystem on the system partition on "usbimage" is at least 4000M large 0.000
And the UUID of the FAT filesystem on the system partition on "usbimage" was randomized 0.000
And the label of the FAT filesystem on the system partition on "usbimage" is "TAILS" 0.000
And the system partition on "usbimage" has the expected flags 0.000
After features/support/hooks.rb:305 3.921 
SCENARIO FAILED: 'The system partition is updated when booting from a USB drive where a Tails USB image was copied' (at time 01:10:16)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4857/artifact/build-artifacts/01:10:16_The_system_partition_is_updated_when_booting_from_a_USB_drive_where_a_Tails_USB_image_was_copied.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4857/artifact/build-artifacts/01:10:16_The_system_partition_is_updated_when_booting_from_a_USB_drive_where_a_Tails_USB_image_was_copied.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4857/artifact/build-artifacts/01:10:16_The_system_partition_is_updated_when_booting_from_a_USB_drive_where_a_Tails_USB_image_was_copied.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4857/artifact/build-artifacts/01:10:16_The_system_partition_is_updated_when_booting_from_a_USB_drive_where_a_Tails_USB_image_was_copied.journal
After features/support/hooks.rb:89 0.006
Feature: Tails-related cryptographic keys are up-to-date
Tags: @product
22.601
Scenario The included APT repository keys are up-to-date
Before features/support/hooks.rb:259 0.005
Steps
Given I have started Tails from DVD without network and logged in 9.042
Then the keys trusted by APT are valid for the next 3 months 13.558
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.461 
SCENARIO FAILED: 'The included APT repository keys are up-to-date' (at time 02:23:26)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4857/artifact/build-artifacts/02:23:26_The_included_APT_repository_keys_are_up-to-date.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4857/artifact/build-artifacts/02:23:26_The_included_APT_repository_keys_are_up-to-date.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4857/artifact/build-artifacts/02:23:26_The_included_APT_repository_keys_are_up-to-date.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4857/artifact/build-artifacts/02:23:26_The_included_APT_repository_keys_are_up-to-date.journal
After features/support/hooks.rb:89 0.000