Project Number Date
test_Tails_ISO_20530-tca-controls-tor-flag-file 4 31 Oct 2024, 22:37

Failures Overview

The following summary displays scenarios that failed.

Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
54.430
Scenario Erasure of read and write disk caches on unmount: LUKS-encrypted ext4
Before features/support/hooks.rb:269 0.002
Steps
Given I have started Tails from DVD without network and logged in 8.317
And I prepare Tails for memory erasure tests 0.588
When I plug and mount a 128 MiB USB drive with an ext4 filesystem encrypted with password "asdf" 45.525
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:784:in `deal_with_polkit_prompt'
./features/step_definitions/common_steps.rb:1486:in `/^I plug and mount a (\d+) MiB USB drive with an? (.*)$/'
features/erase_memory.feature:50:in `When I plug and mount a 128 MiB USB drive with an ext4 filesystem encrypted with password "asdf"'
Then I find very few patterns in the guest's memory 0.000
# write cache
When I fill the USB drive with a known pattern 0.000
Then patterns cover at least 99% of the test FS size in the guest's memory 0.000
When I umount the USB drive 0.000
Then I find very few patterns in the guest's memory after 3 seconds 0.000
# read cache
When I mount the USB drive again 0.000
And I read the content of the test FS 0.000
Then patterns cover at least 99% of the test FS size in the guest's memory 0.000
When I umount the USB drive 0.000
Then I find very few patterns in the guest's memory after 3 seconds 0.000
After features/support/hooks.rb:326 7.517 
SCENARIO FAILED: 'Erasure of read and write disk caches on unmount: LUKS-encrypted ext4' (at time 00:31:47)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/4/artifact/build-artifacts/00:31:47_Erasure_of_read_and_write_disk_caches_on_unmount:_LUKS-encrypted_ext4.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/4/artifact/build-artifacts/00:31:47_Erasure_of_read_and_write_disk_caches_on_unmount:_LUKS-encrypted_ext4.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/4/artifact/build-artifacts/00:31:47_Erasure_of_read_and_write_disk_caches_on_unmount:_LUKS-encrypted_ext4.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/4/artifact/build-artifacts/00:31:47_Erasure_of_read_and_write_disk_caches_on_unmount:_LUKS-encrypted_ext4.journal
After features/support/hooks.rb:100 0.002
Feature: Installing Tails to a USB drive
Tags: @product @uefi
3:14.084
Scenario Booting Tails from a USB drive in UEFI mode
Before features/support/hooks.rb:269 0.002
Steps
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.143
And I power off the computer 0.339
And the computer is set to boot in UEFI mode 0.045
When I start Tails from USB drive "__internal" with network unplugged and I login 3:1.556
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:240:in `rescue in wait_any'
./features/support/helpers/screen.rb:224: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.537 
SCENARIO FAILED: 'Booting Tails from a USB drive in UEFI mode' (at time 00:59:01)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/4/artifact/build-artifacts/00:59:01_Booting_Tails_from_a_USB_drive_in_UEFI_mode.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/4/artifact/build-artifacts/00:59:01_Booting_Tails_from_a_USB_drive_in_UEFI_mode.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/4/artifact/build-artifacts/00:59:01_Booting_Tails_from_a_USB_drive_in_UEFI_mode.journal
After features/support/hooks.rb:100 0.054
Feature: Packages are up-to-date
Tags: @source
3.786
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.786
Command 
Command failed (returned pid 56390 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20530-tca-controls-tor-flag-file/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_20530-tca-controls-tor-flag-file/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_20530-tca-controls-tor-flag-file/tmp/tails-amd64-20530-tca-controls-tor-flag-file@8e14d5aed2+stable@85b3d133b7-20241031T1705Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_20530-tca-controls-tor-flag-file/tmp/tails-amd64-20530-tca-controls-tor-flag-file@8e14d5aed2+stable@85b3d133b7-20241031T1705Z.build-manifest
INFO: Need to upgrade to a new APT snapshot:
  - firmware-nonfree (20240909-1) to Debian sid (20240909-2)
.
<0> expected but was
<#<Process::Status: pid 56390 exit 1>>. (Test::Unit::AssertionFailedError)
/var/lib/jenkins/workspace/test_Tails_ISO_20530-tca-controls-tor-flag-file/features/support/helpers/misc_helpers.rb:307:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_20530-tca-controls-tor-flag-file/features/support/helpers/misc_helpers.rb:303:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_20530-tca-controls-tor-flag-file/features/support/helpers/misc_helpers.rb:303:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_20530-tca-controls-tor-flag-file/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