Project Number Date
test_Tails_ISO_20524-warn-danger-unplug-usb-stick 46 26 Nov 2024, 07:18

Failures Overview

The following summary displays scenarios that failed.

Feature: Installing Tails to a USB drive
Tags: @product @uefi
3:13.650
Scenario Booting Tails from a USB drive in UEFI mode
Before features/support/hooks.rb:269 0.003
Steps
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 11.822
And I power off the computer 0.346
And the computer is set to boot in UEFI mode 0.027
When I start Tails from USB drive "__internal" with network unplugged and I login 3:1.453
try_for() 
try_for() timeout expired
Last ignored exception was: FindFailed: can not find any of the patterns ["TailsBootMenuGRUB_Bullseye.png", "TailsBootMenuGRUB_Bookworm.png"] on the screen
./features/support/helpers/screen.rb:246:in `rescue in wait_any'
./features/support/helpers/screen.rb:230:in `wait_any'
./features/step_definitions/common_steps.rb:407:in `block in enter_boot_menu_cmdline'
./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/common_steps.rb:404:in `enter_boot_menu_cmdline'
./features/step_definitions/common_steps.rb:434:in `the_computer_boots'
./features/step_definitions/common_steps.rb:448:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:284: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/common_steps.rb:404:in `enter_boot_menu_cmdline'
./features/step_definitions/common_steps.rb:434:in `the_computer_boots'
./features/step_definitions/common_steps.rb:448:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:284: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/usb_install.feature:85:in `When I start Tails from USB drive "__internal" with network unplugged and I login'
Then Tails is running from USB drive "__internal" 0.000
And the boot device has safe access rights 0.000
And Tails has started in UEFI mode 0.000
After features/support/hooks.rb:326 10.595 
SCENARIO FAILED: 'Booting Tails from a USB drive in UEFI mode' (at time 00:59:17)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/46/artifact/build-artifacts/00:59:17_Booting_Tails_from_a_USB_drive_in_UEFI_mode.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/46/artifact/build-artifacts/00:59:17_Booting_Tails_from_a_USB_drive_in_UEFI_mode.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/46/artifact/build-artifacts/00:59:17_Booting_Tails_from_a_USB_drive_in_UEFI_mode.journal
After features/support/hooks.rb:100 0.063
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
2:57.283
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.008
Before features/support/hooks.rb:507 0.007
Steps
Given a computer 0.249
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 2:57.034
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/step_definitions/common_steps.rb:300: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/additional_software_packages.feature:79:in `And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password'
And I configure APT to prefer an old version of cowsay 0.000
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 0.000
And I accept adding "cowsay" to Additional Software 0.000
And Additional Software is correctly configured for package "cowsay" 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
# 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.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
# 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.000
And the network is plugged 0.000
And Tor is ready 0.000
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.038
After features/support/hooks.rb:326 14.219 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:22:52)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/46/artifact/build-artifacts/01:22:52_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_20524-warn-danger-unplug-usb-stick/46/artifact/build-artifacts/01:22:52_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_20524-warn-danger-unplug-usb-stick/46/artifact/build-artifacts/01:22:52_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_20524-warn-danger-unplug-usb-stick/46/artifact/build-artifacts/01:22:52_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.008
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited
6:52.518
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.005
Steps
Given a computer 0.215
And I start Tails from USB drive "__internal" with network unplugged 1:9.106
And I enable persistence 13.425
And I remove the "cowsay" deb files from the APT cache 0.053
# 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.084
And I log in to a new session 28.719
Then I see the "The installation of your additional software failed" notification after at most 300 seconds 5:0.914
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/step_definitions/common_steps.rb:592:in `/^I see the "(.+)" notification(?: after at most (\d+) seconds)?$/'
features/additional_software_packages.feature:129: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:515 0.039
After features/support/hooks.rb:326 8.663 
SCENARIO FAILED: 'I am notified when Additional Software fails to install a package' (at time 01:29:58)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/46/artifact/build-artifacts/01:29:58_I_am_notified_when_Additional_Software_fails_to_install_a_package.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/46/artifact/build-artifacts/01:29:58_I_am_notified_when_Additional_Software_fails_to_install_a_package.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/46/artifact/build-artifacts/01:29:58_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
6.038
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 6.038
Command 
Command failed (returned pid 63515 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/tmp/tails-amd64-20524-warn-danger-unplug-usb-stick@c782b03dc7+stable@a98e48ea10-20241126T0152Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/tmp/tails-amd64-20524-warn-danger-unplug-usb-stick@c782b03dc7+stable@a98e48ea10-20241126T0152Z.build-manifest
INFO: Need to upgrade to a new APT snapshot:
  - blinker (1.8.2-1) to Debian trixie (1.9.0-1)
  - firmware-sof (2024.06-2) to Debian trixie (2024.09.1-1)
.
<0> expected but was
<#<Process::Status: pid 63515 exit 1>>. (Test::Unit::AssertionFailedError)
/var/lib/jenkins/workspace/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/features/support/helpers/misc_helpers.rb:307:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/features/support/helpers/misc_helpers.rb:303:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/features/support/helpers/misc_helpers.rb:303:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_20524-warn-danger-unplug-usb-stick/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