Project Number Date
test_Tails_ISO_stable 5461 16 Feb 2025, 12:30

Failures Overview

The following summary displays scenarios that failed.

Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
8:12.090
Scenario Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online
Before features/support/hooks.rb:269 0.003
Before features/support/hooks.rb:507 0.004
Steps
Given a computer 0.276
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 2:16.753
And I configure APT to prefer an old version of cowsay 0.031
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 26.536
And I accept adding "cowsay" to Additional Software 6.540
And Additional Software is correctly configured for package "cowsay" 0.911
And I shutdown Tails and wait for the computer to power off 6.694
And I start Tails from USB drive "__internal" with network unplugged 59.892
And I enable persistence 10.947
# We need to add back this custom APT source for the Additional Software
# install step, as it was not saved in persistence
And I configure APT to prefer an old version of cowsay 0.025
# 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.090
And I log in to a new session 38.376
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 2:23.491
And I revert the APT tweaks that made it prefer an old version of cowsay 0.055
# We remove the newest package after it has been downloaded and before
# it is installed, so that the upgrade process fails
And I prepare the Additional Software upgrade process to fail 0.068
And the network is plugged 0.060
And Tor is ready 1:1.339
TCA 
TCA did not start (TorBootstrapFailure)
./features/step_definitions/tor.rb:375:in `rescue in block in <top (required)>'
./features/step_definitions/tor.rb:371:in `/^the Tor Connection Assistant (?:autostarts|is running)$/'
./features/step_definitions/common_steps.rb:645:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:600:in `/^Tor is ready$/'
features/additional_software_packages.feature:100:in `And Tor is ready'
And available upgrades have been checked 0.000
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 0.000
And I can open the Additional Software configuration window from the notification 0.000
And I shutdown Tails and wait for the computer to power off 0.000
And I start Tails from USB drive "__internal" with network unplugged 0.000
And I enable persistence 0.000
# We need to add back this custom APT source for the Additional Software
# install step, as it was not saved in persistence
And I configure APT to prefer an old version of cowsay 0.000
And I log in to a new session 0.000
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 0.000
And I revert the APT tweaks that made it prefer an old version of cowsay 0.000
And the network is plugged 0.000
And Tor is ready 0.000
Then the Additional Software upgrade service has started 0.000
And the installed version of package "cowsay" is newer than "3.03+dfsg2-1" 0.000
After features/support/hooks.rb:515 0.036
After features/support/hooks.rb:326 14.177 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:20:11)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5461/artifact/build-artifacts/01:20:11_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online_chutney-data
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5461/artifact/build-artifacts/01:20:11_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5461/artifact/build-artifacts/01:20:11_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5461/artifact/build-artifacts/01:20:11_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.journal
After features/support/hooks.rb:100 0.016
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited
3:13.206
Scenario I am notified when Additional Software fails to install a package
Before features/support/hooks.rb:269 0.004
Before features/support/hooks.rb:507 0.006
Steps
Given a computer 0.186
And I start Tails from USB drive "__internal" with network unplugged 1:1.660
And I enable persistence 13.379
And I remove the "cowsay" deb files from the APT cache 0.054
# 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.083
And I log in to a new session 44.166
Then I see the "The installation of your additional software failed" notification after at most 300 seconds 12.793
And I can open the Additional Software log file from the notification 1:0.881
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.055
After features/support/hooks.rb:326 8.610 
SCENARIO FAILED: 'I am notified when Additional Software fails to install a package' (at time 01:23:38)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5461/artifact/build-artifacts/01:23:38_I_am_notified_when_Additional_Software_fails_to_install_a_package.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5461/artifact/build-artifacts/01:23:38_I_am_notified_when_Additional_Software_fails_to_install_a_package.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5461/artifact/build-artifacts/01:23:38_I_am_notified_when_Additional_Software_fails_to_install_a_package.journal
After features/support/hooks.rb:100 0.007
Feature: Packages are up-to-date
Tags: @source
3.387
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 3.387
Command 
Command failed (returned pid 57008 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_stable/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_stable/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_stable/tmp/tails-amd64-stable@3367737e1d-20250216T0716Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_stable/tmp/tails-amd64-stable@3367737e1d-20250216T0716Z.build-manifest
INFO: Need to upgrade to a new APT snapshot:
  - onionshare (2.6.2-1~0.tails1) to Debian trixie (2.6.2-5)
  - ublock-origin (1.60.0+dfsg-1) to Debian trixie (1.62.0+dfsg-1)
.
<0> expected but was
<#<Process::Status: pid 57008 exit 1>>. (Test::Unit::AssertionFailedError)
/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/support/helpers/misc_helpers.rb:307:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/support/helpers/misc_helpers.rb:303:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/support/helpers/misc_helpers.rb:303:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_stable/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