Project Number Date
test_Tails_ISO_stable 4824 02 May 2024, 18:06

Failures Overview

The following summary displays scenarios that failed.

Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited
2:5.490
Scenario I am notified when Additional Software fails to install a package
Before features/support/hooks.rb:259 0.005
Before features/support/hooks.rb:456 0.007
Steps
Given a computer 0.186
And I start Tails from USB drive "__internal" with network unplugged 59.977
And I enable persistence 13.461
And I remove the "cowsay" deb files from the APT cache 0.666
# Prevent the "Warning: virtual machine detected!" notification from racing
# with the one we'll be interacting with below.
And I disable the tails-virt-notify-user.service user unit 0.104
And I log in to a new session 39.933
Then I see the "The installation of your additional software failed" notification after at most 300 seconds 11.160
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:587:in `new'
./features/step_definitions/common_steps.rb:587:in `/^I see the "(.+)" notification(?: after at most (\d+) seconds)?$/'
features/additional_software_packages.feature:132:in `Then I see the "The installation of your additional software failed" notification after at most 300 seconds'
And I can open the Additional Software log file from the notification 0.000
And the package "cowsay" is not installed 0.000
After features/support/hooks.rb:464 0.045
After features/support/hooks.rb:305 4.593 
SCENARIO FAILED: 'I am notified when Additional Software fails to install a package' (at time 01:36:22)
Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4824/artifact/build-artifacts/01:36:22_I_am_notified_when_Additional_Software_fails_to_install_a_package.file_content_run_live-additional-software_log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4824/artifact/build-artifacts/01:36:22_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4824/artifact/build-artifacts/01:36:22_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4824/artifact/build-artifacts/01:36:22_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4824/artifact/build-artifacts/01:36:22_I_am_notified_when_Additional_Software_fails_to_install_a_package.cmd_output_mount
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4824/artifact/build-artifacts/01:36:22_I_am_notified_when_Additional_Software_fails_to_install_a_package.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4824/artifact/build-artifacts/01:36:22_I_am_notified_when_Additional_Software_fails_to_install_a_package.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4824/artifact/build-artifacts/01:36:22_I_am_notified_when_Additional_Software_fails_to_install_a_package.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4824/artifact/build-artifacts/01:36:22_I_am_notified_when_Additional_Software_fails_to_install_a_package.journal
After features/support/hooks.rb:89 0.011
Feature: Tails-related cryptographic keys are up-to-date
Tags: @product
21.422
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 8.143
Then the keys trusted by APT are valid for the next 3 months 13.278
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.391 
SCENARIO FAILED: 'The included APT repository keys are up-to-date' (at time 02:19:09)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4824/artifact/build-artifacts/02:19:09_The_included_APT_repository_keys_are_up-to-date.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4824/artifact/build-artifacts/02:19:09_The_included_APT_repository_keys_are_up-to-date.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4824/artifact/build-artifacts/02:19:09_The_included_APT_repository_keys_are_up-to-date.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4824/artifact/build-artifacts/02:19:09_The_included_APT_repository_keys_are_up-to-date.journal
After features/support/hooks.rb:89 0.000
Feature: Tails persistence
Tags: @product
10:9.840
Scenario LUKS header is automatically upgraded when unlocking the Persistent Storage
Before features/support/hooks.rb:259 0.006
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 6:22.140
And I enable persistence 43.662
And I log in to a new session after having activated the Persistent Storage 3:4.036
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 4.584 
SCENARIO FAILED: 'LUKS header is automatically upgraded when unlocking the Persistent Storage' (at time 03:36:54)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4824/artifact/build-artifacts/03:36:54_LUKS_header_is_automatically_upgraded_when_unlocking_the_Persistent_Storage.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4824/artifact/build-artifacts/03:36:54_LUKS_header_is_automatically_upgraded_when_unlocking_the_Persistent_Storage.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4824/artifact/build-artifacts/03:36:54_LUKS_header_is_automatically_upgraded_when_unlocking_the_Persistent_Storage.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4824/artifact/build-artifacts/03:36:54_LUKS_header_is_automatically_upgraded_when_unlocking_the_Persistent_Storage.journal
After features/support/hooks.rb:89 0.000