Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 61 01 May 2024, 06:36

Failures Overview

The following summary displays scenarios that failed.

Feature: Tails-related cryptographic keys are up-to-date
Tags: @product
20.802
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.150
Then the keys trusted by APT are valid for the next 3 months 12.651
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.498 
SCENARIO FAILED: 'The included APT repository keys are up-to-date' (at time 02:15:39)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/61/artifact/build-artifacts/02:15:39_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/61/artifact/build-artifacts/02:15:39_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/61/artifact/build-artifacts/02:15:39_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/61/artifact/build-artifacts/02:15:39_The_included_APT_repository_keys_are_up-to-date.journal
After features/support/hooks.rb:89 0.000
Feature: Tails persistence
Tags: @product
2:45.878
Scenario Dotfiles persistence
Before features/support/hooks.rb:259 0.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.073
When I write some dotfile expected to persist 0.230
And I shutdown Tails and wait for the computer to power off 9.330
And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:26.244
The 
The Dogtail init script raised: SearchError: child of [desktop frame | main]: "gnome-shell" application
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:711:in `new'
./features/step_definitions/common_steps.rb:711:in `/^all notifications have disappeared$/'
./features/step_definitions/common_steps.rb:295: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/persistence.feature:139:in `And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
Then the expected persistent dotfile is present in the filesystem 0.000
After features/support/hooks.rb:305 4.457 
SCENARIO FAILED: 'Dotfiles persistence' (at time 03:25:30)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/61/artifact/build-artifacts/03:25:30_Dotfiles_persistence.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/61/artifact/build-artifacts/03:25:30_Dotfiles_persistence.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/61/artifact/build-artifacts/03:25:30_Dotfiles_persistence.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/61/artifact/build-artifacts/03:25:30_Dotfiles_persistence.journal
After features/support/hooks.rb:89 0.009