Project Number Date
test_Tails_ISO_stable 4822 02 May 2024, 12:23

Failures Overview

The following summary displays scenarios that failed.

Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited
2:8.698
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.190
And I start Tails from USB drive "__internal" with network unplugged 1:0.882
And I enable persistence 14.263
And I remove the "cowsay" deb files from the APT cache 0.894
# 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.087
And I log in to a new session 41.505
Then I see the "The installation of your additional software failed" notification after at most 300 seconds 10.875
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.037
After features/support/hooks.rb:305 5.035 
SCENARIO FAILED: 'I am notified when Additional Software fails to install a package' (at time 01:33:15)
Content of /run/live-additional-software/log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4822/artifact/build-artifacts/01:33:15_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/4822/artifact/build-artifacts/01:33:15_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/4822/artifact/build-artifacts/01:33:15_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/4822/artifact/build-artifacts/01:33:15_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/4822/artifact/build-artifacts/01:33:15_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/4822/artifact/build-artifacts/01:33:15_I_am_notified_when_Additional_Software_fails_to_install_a_package.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4822/artifact/build-artifacts/01:33:15_I_am_notified_when_Additional_Software_fails_to_install_a_package.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4822/artifact/build-artifacts/01:33:15_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/4822/artifact/build-artifacts/01:33:15_I_am_notified_when_Additional_Software_fails_to_install_a_package.journal
After features/support/hooks.rb:89 0.009
Feature: Tails-related cryptographic keys are up-to-date
Tags: @product
22.701
Scenario The included APT repository keys are up-to-date
Before features/support/hooks.rb:259 0.007
Steps
Given I have started Tails from DVD without network and logged in 8.420
Then the keys trusted by APT are valid for the next 3 months 14.280
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.356 
SCENARIO FAILED: 'The included APT repository keys are up-to-date' (at time 02:16:20)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4822/artifact/build-artifacts/02:16:20_The_included_APT_repository_keys_are_up-to-date.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4822/artifact/build-artifacts/02:16:20_The_included_APT_repository_keys_are_up-to-date.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4822/artifact/build-artifacts/02:16:20_The_included_APT_repository_keys_are_up-to-date.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4822/artifact/build-artifacts/02:16:20_The_included_APT_repository_keys_are_up-to-date.journal
After features/support/hooks.rb:89 0.000
Feature: Tails persistence
Tags: @product
3:15.796
Scenario Changing the Persistent Storage passphrase
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 14.259
# Note that if anything fails after the passphrase was changed and
# before it's changed back below, subsequent scenarios might fail
# because the Persistent Storage doesn't have the expected passphrase.
When I change the passphrase of the Persistent Storage 33.082
And I shutdown Tails and wait for the computer to power off 12.583
Then I start Tails from USB drive "__internal" with network unplugged and I login with the changed persistence passphrase 2:15.870
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:123:in `Then I start Tails from USB drive "__internal" with network unplugged and I login with the changed persistence passphrase'
And I change the passphrase of the Persistent Storage back to the original 0.000
After features/support/hooks.rb:305 4.480 
SCENARIO FAILED: 'Changing the Persistent Storage passphrase' (at time 03:21:56)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4822/artifact/build-artifacts/03:21:56_Changing_the_Persistent_Storage_passphrase.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4822/artifact/build-artifacts/03:21:56_Changing_the_Persistent_Storage_passphrase.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4822/artifact/build-artifacts/03:21:56_Changing_the_Persistent_Storage_passphrase.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4822/artifact/build-artifacts/03:21:56_Changing_the_Persistent_Storage_passphrase.journal
After features/support/hooks.rb:89 0.010
Feature: Tails persistence
Tags: @product
2:34.524
Scenario Dotfiles persistence
Before features/support/hooks.rb:259 0.008
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.599
When I write some dotfile expected to persist 0.111
And I shutdown Tails and wait for the computer to power off 8.631
And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 2:16.181
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.679 
SCENARIO FAILED: 'Dotfiles persistence' (at time 03:25:41)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4822/artifact/build-artifacts/03:25:41_Dotfiles_persistence.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4822/artifact/build-artifacts/03:25:41_Dotfiles_persistence.mkv
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4822/artifact/build-artifacts/03:25:41_Dotfiles_persistence.boot-log
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/4822/artifact/build-artifacts/03:25:41_Dotfiles_persistence.journal
After features/support/hooks.rb:89 0.010