Project Number Date
test_Tails_ISO_devel 3691 14 Feb 2025, 13:05

Failures Overview

The following summary displays scenarios that failed.

Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited
3:9.174
Scenario I am notified when Additional Software fails to install a package
Before features/support/hooks.rb:269 0.005
Before features/support/hooks.rb:507 0.006
Steps
Given a computer 0.251
And I start Tails from USB drive "__internal" with network unplugged 1:8.639
And I enable persistence 12.689
And I remove the "cowsay" deb files from the APT cache 0.052
# 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.085
And I log in to a new session 40.334
Then I see the "The installation of your additional software failed" notification after at most 300 seconds 6.383
And I can open the Additional Software log file from the notification 1:0.739
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: child of [desktop frame | main]: "gnome-text-editor" application
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/additional_software_packages.rb:171:in `new'
./features/step_definitions/additional_software_packages.rb:171:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/additional_software_packages.rb:170:in `block in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/additional_software_packages.rb:170:in `/^I can open the Additional Software log file from the notification$/'
features/additional_software_packages.feature:130:in `And I can open the Additional Software log file from the notification'
And the package "cowsay" is not installed 0.000
After features/support/hooks.rb:515 0.035
After features/support/hooks.rb:326 8.261 
SCENARIO FAILED: 'I am notified when Additional Software fails to install a package' (at time 01:30:38)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3691/artifact/build-artifacts/01:30:38_I_am_notified_when_Additional_Software_fails_to_install_a_package.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3691/artifact/build-artifacts/01:30:38_I_am_notified_when_Additional_Software_fails_to_install_a_package.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3691/artifact/build-artifacts/01:30:38_I_am_notified_when_Additional_Software_fails_to_install_a_package.journal
After features/support/hooks.rb:100 0.009
Feature: Packages are up-to-date
Tags: @source
14.670
Scenario All packages are up-to-date
Before features/support/hooks.rb:532 0.000
Steps
Given I have the build manifest for the image under test 0.000
Then all packages listed in the build manifest are up-to-date 14.670
Command 
Command failed (returned pid 57882 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_devel/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_devel/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_devel/tmp/tails-amd64-devel@7f3c9d76c9-20250214T0657Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_devel/tmp/tails-amd64-devel@7f3c9d76c9-20250214T0657Z.build-manifest
INFO: Need to upgrade to a new APT snapshot:
  - onionshare (2.6.2-1~0.tails1) to Debian sid (2.6.2-5)
.
<0> expected but was
<#<Process::Status: pid 57882 exit 1>>. (Test::Unit::AssertionFailedError)
/var/lib/jenkins/workspace/test_Tails_ISO_devel/features/support/helpers/misc_helpers.rb:307:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_devel/features/support/helpers/misc_helpers.rb:303:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_devel/features/support/helpers/misc_helpers.rb:303:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_devel/features/step_definitions/needed_package_updates.rb:8:in `/^all packages listed in the build manifest are up-to-date$/'
features/needed_package_updates.feature:12:in `Then all packages listed in the build manifest are up-to-date'
After features/support/hooks.rb:539 0.000
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
2:27.970
Scenario Changing the Persistent Storage passphrase
Before features/support/hooks.rb:269 0.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.604
# 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 50.111
And I shutdown Tails and wait for the computer to power off 12.592
Then I start Tails from USB drive "__internal" with network unplugged and I login with the changed persistence passphrase 1:13.662
try_for() 
try_for() timeout expired (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/support/helpers/dogtail.rb:357:in `grabFocus'
./features/step_definitions/usb.rb:672:in `/^I try to enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:703:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/common_steps.rb:292: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:326 4.857 
SCENARIO FAILED: 'Changing the Persistent Storage passphrase' (at time 03:34:12)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3691/artifact/build-artifacts/03:34:12_Changing_the_Persistent_Storage_passphrase.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3691/artifact/build-artifacts/03:34:12_Changing_the_Persistent_Storage_passphrase.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3691/artifact/build-artifacts/03:34:12_Changing_the_Persistent_Storage_passphrase.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3691/artifact/build-artifacts/03:34:12_Changing_the_Persistent_Storage_passphrase.journal
After features/support/hooks.rb:100 0.009