Project Number Date
test_Tails_ISO_stable 4827 05 May 2024, 12:13

Failures Overview

The following summary displays scenarios that failed.

Feature: Tails-related cryptographic keys are up-to-date
Tags: @product
21.184
Scenario The included APT repository keys are up-to-date
Before features/support/hooks.rb:259 0.006
Steps
Given I have started Tails from DVD without network and logged in 8.038
Then the keys trusted by APT are valid for the next 3 months 13.145
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.452 
SCENARIO FAILED: 'The included APT repository keys are up-to-date' (at time 02:11:55)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4827/artifact/build-artifacts/02:11:55_The_included_APT_repository_keys_are_up-to-date.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4827/artifact/build-artifacts/02:11:55_The_included_APT_repository_keys_are_up-to-date.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4827/artifact/build-artifacts/02:11:55_The_included_APT_repository_keys_are_up-to-date.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4827/artifact/build-artifacts/02:11:55_The_included_APT_repository_keys_are_up-to-date.journal
After features/support/hooks.rb:89 0.000
Feature: Tails persistence
Tags: @product
6:41.572
Scenario LUKS header is automatically upgraded when unlocking the Persistent Storage
Before features/support/hooks.rb:259 0.014
Steps
Given I have started Tails without network from a USB drive with a LUKS 1 persistent partition and stopped at Tails Greeter's login screen 3:2.617
And I enable persistence 34.975
And I log in to a new session after having activated the Persistent Storage 3:3.979
cannot 
cannot find GnomeApplicationsMenu.png on the screen (FindFailed)
./features/support/helpers/screen.rb:173:in `rescue in wait'
./features/support/helpers/screen.rb:157:in `wait'
./features/step_definitions/common_steps.rb:558:in `/^the Tails desktop is ready$/'
./features/step_definitions/common_steps.rb:514:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
features/persistence.feature:156:in `And I log in to a new session after having activated the Persistent Storage'
Then a Tails persistence partition with LUKS version 2 and argon2id exists on USB drive "__internal" 0.000
And persistence is enabled 0.000
After features/support/hooks.rb:305 5.051 
SCENARIO FAILED: 'LUKS header is automatically upgraded when unlocking the Persistent Storage' (at time 03:26:25)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4827/artifact/build-artifacts/03:26:25_LUKS_header_is_automatically_upgraded_when_unlocking_the_Persistent_Storage.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4827/artifact/build-artifacts/03:26:25_LUKS_header_is_automatically_upgraded_when_unlocking_the_Persistent_Storage.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4827/artifact/build-artifacts/03:26:25_LUKS_header_is_automatically_upgraded_when_unlocking_the_Persistent_Storage.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4827/artifact/build-artifacts/03:26:25_LUKS_header_is_automatically_upgraded_when_unlocking_the_Persistent_Storage.journal
After features/support/hooks.rb:89 0.000