Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 123 01 Jul 2024, 06:46

Failures Overview

The following summary displays scenarios that failed.

Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
20.283
Scenario Erasure of memory freed by killed userspace processes
Before features/support/hooks.rb:269 0.002
Steps
Given I have started Tails from DVD without network and logged in 9.610
And I prepare Tails for memory erasure tests 0.498
When I start a process allocating 128 MiB of memory with a known pattern 2.306
Then patterns cover at least 128 MiB in the guest's memory 3.225 
Pattern coverage: 100.000% (128 MiB out of 128 MiB reference memory)
When I kill the allocating process 0.394
Then I find very few patterns in the guest's memory 4.247
9.414% 
9.414% of the free memory still has the pattern, but less than 0.800% was expected.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/erase_memory.rb:219:in `/^I find very few patterns in the guest's memory$/'
features/erase_memory.feature:19:in `Then I find very few patterns in the guest's memory'
Output 1 
Pattern coverage: 9.414% (82 MiB out of 876 MiB reference memory)
After features/support/hooks.rb:326 5.106 
SCENARIO FAILED: 'Erasure of memory freed by killed userspace processes' (at time 00:31:03)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/123/artifact/build-artifacts/00:31:03_Erasure_of_memory_freed_by_killed_userspace_processes.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/123/artifact/build-artifacts/00:31:03_Erasure_of_memory_freed_by_killed_userspace_processes.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/123/artifact/build-artifacts/00:31:03_Erasure_of_memory_freed_by_killed_userspace_processes.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/123/artifact/build-artifacts/00:31:03_Erasure_of_memory_freed_by_killed_userspace_processes.journal
After features/support/hooks.rb:100 0.000
Feature: Using Evince
Tags: @product @not_release_blocker
35.328
Scenario I cannot view a PDF file stored in non-persistent /home/amnesia/.gnupg
Before features/support/hooks.rb:269 0.005
Steps
Given I have started Tails from DVD without network and logged in 8.677
And I copy "/usr/share/cups/data/default-testpage.pdf" to "/home/amnesia/.gnupg" as user "amnesia" 0.169
Then the file "/home/amnesia/.gnupg/default-testpage.pdf" exists 0.054
And the file "/lib/live/mount/overlay/rw/home/amnesia/.gnupg/default-testpage.pdf" exists after at most 10 seconds 0.056
And the file "/live/overlay/rw/home/amnesia/.gnupg/default-testpage.pdf" exists after at most 10 seconds 0.067
Given I start monitoring the AppArmor log of "/usr/bin/evince" 0.201
When I try to open "/home/amnesia/.gnupg/default-testpage.pdf" with Evince 3.521
Then Evince tells me it cannot open "/home/amnesia/.gnupg/default-testpage.pdf" 2.353
And AppArmor has denied "/usr/bin/evince" from opening "/home/amnesia/.gnupg/default-testpage.pdf" 0.081
When I close Evince 20.144
Process 
Process 'evince' is still running after waiting for 20 seconds (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:817:in `/^process "([^"]+)" has stopped running after at most (\d+) seconds$/'
./features/step_definitions/evince.rb:34:in `/^I close Evince$/'
features/evince.feature:31:in `When I close Evince'
Given I restart monitoring the AppArmor log of "/usr/bin/evince" 0.000
When I try to open "/lib/live/mount/overlay/rw/home/amnesia/.gnupg/default-testpage.pdf" with Evince 0.000
Then Evince tells me it cannot open "/lib/live/mount/overlay/rw/home/amnesia/.gnupg/default-testpage.pdf" 0.000
And AppArmor has denied "/usr/bin/evince" from opening "/usr/lib/live/mount/overlay/rw/home/amnesia/.gnupg/default-testpage.pdf" 0.000
When I close Evince 0.000
Given I restart monitoring the AppArmor log of "/usr/bin/evince" 0.000
When I try to open "/live/overlay/rw/home/amnesia/.gnupg/default-testpage.pdf" with Evince 0.000
Then Evince tells me it cannot open "/live/overlay/rw/home/amnesia/.gnupg/default-testpage.pdf" 0.000
# Due to our AppArmor aliases, /live/overlay will be treated
# as /usr/lib/live/mount/overlay.
And AppArmor has denied "/usr/bin/evince" from opening "/usr/lib/live/mount/overlay/rw/home/amnesia/.gnupg/default-testpage.pdf" 0.000
After features/support/hooks.rb:326 5.098 
SCENARIO FAILED: 'I cannot view a PDF file stored in non-persistent /home/amnesia/.gnupg' (at time 02:10:36)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/123/artifact/build-artifacts/02:10:36_I_cannot_view_a_PDF_file_stored_in_non-persistent__home_amnesia_.gnupg.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/123/artifact/build-artifacts/02:10:36_I_cannot_view_a_PDF_file_stored_in_non-persistent__home_amnesia_.gnupg.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/123/artifact/build-artifacts/02:10:36_I_cannot_view_a_PDF_file_stored_in_non-persistent__home_amnesia_.gnupg.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/123/artifact/build-artifacts/02:10:36_I_cannot_view_a_PDF_file_stored_in_non-persistent__home_amnesia_.gnupg.journal
After features/support/hooks.rb:100 0.000
Feature: Packages are up-to-date
Tags: @source
3.055
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.055
Command 
Command failed (returned pid 50045 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20268-more-early-patch-functionality/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_20268-more-early-patch-functionality/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_20268-more-early-patch-functionality/tmp/tails-amd64-20268-more-early-patch-functionality@3fb49bb945+stable@7fdcb6570f-20240701T0131Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_20268-more-early-patch-functionality/tmp/tails-amd64-20268-more-early-patch-functionality@3fb49bb945+stable@7fdcb6570f-20240701T0131Z.build-manifest
INFO: Need to upgrade to a new APT snapshot:
  - wpa (2:2.10-12) to Debian bookworm (2:2.10-12+deb12u1)
.
<0> expected but was
<#<Process::Status: pid 50045 exit 1>>. (Test::Unit::AssertionFailedError)
/var/lib/jenkins/workspace/test_Tails_ISO_20268-more-early-patch-functionality/features/support/helpers/misc_helpers.rb:307:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_20268-more-early-patch-functionality/features/support/helpers/misc_helpers.rb:303:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_20268-more-early-patch-functionality/features/support/helpers/misc_helpers.rb:303:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_20268-more-early-patch-functionality/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