Project Number Date
test_Tails_ISO_20660-fix-random-seed-update 3 11 Nov 2024, 16:58

Failures Overview

The following summary displays scenarios that failed.

Tags: @product
2:2.385
Scenario I can perform administrative tasks if I have set up an administration password in the Welcome Screen
Before features/support/hooks.rb:269 0.002
Steps
Given I have started Tails from DVD without network and logged in with an administration password 1:56.724
And running a command as root with pkexec requires PolicyKit administrator privileges 0.103
Then I can run a command as root with sudo 0.095
Then I can run a command as root with pkexec 5.462
The
The Dogtail init script raised: Error: atspi_error: timeout from dbind (1)
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:320:in `new'
./features/support/helpers/dogtail.rb:320:in `parent'
./features/step_definitions/common_steps.rb:763:in `gnome_shell_unlock_dialog'
./features/step_definitions/common_steps.rb:780:in `deal_with_polkit_prompt'
./features/step_definitions/common_steps.rb:798:in `/^I enter the "([^"]*)" password in the GNOME authentication prompt$/'
./features/step_definitions/common_steps.rb:757:in `/^I enter the sudo password in the GNOME authentication prompt$/'
./features/step_definitions/root_access_control.rb:50:in `/^I can run a command as root with pkexec$/'
features/root_access_control.feature:10:in `Then I can run a command as root with pkexec'
After features/support/hooks.rb:326 6.246

SCENARIO FAILED: 'I can perform administrative tasks if I have set up an administration password in the Welcome Screen' (at time 00:09:07)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20660-fix-random-seed-update/3/artifact/build-artifacts/00:09:07_I_can_perform_administrative_tasks_if_I_have_set_up_an_administration_password_in_the_Welcome_Screen.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20660-fix-random-seed-update/3/artifact/build-artifacts/00:09:07_I_can_perform_administrative_tasks_if_I_have_set_up_an_administration_password_in_the_Welcome_Screen.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20660-fix-random-seed-update/3/artifact/build-artifacts/00:09:07_I_can_perform_administrative_tasks_if_I_have_set_up_an_administration_password_in_the_Welcome_Screen.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20660-fix-random-seed-update/3/artifact/build-artifacts/00:09:07_I_can_perform_administrative_tasks_if_I_have_set_up_an_administration_password_in_the_Welcome_Screen.journal

After features/support/hooks.rb:100 0.010
26.036
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 13.400
And I prepare Tails for memory erasure tests 0.428
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.408

Pattern coverage: 100.000% (128 MiB out of 128 MiB reference memory)

When I kill the allocating process 0.419
Then I find very few patterns in the guest's memory after 3 seconds 6.072
9.437% 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:222:in `/^I find very few patterns in the guest's memory(?: after (\d+) seconds)?$/'
features/erase_memory.feature:19:in `Then I find very few patterns in the guest's memory after 3 seconds'
Output 1

Pattern coverage: 9.437% (82 MiB out of 873 MiB reference memory)

After features/support/hooks.rb:326 5.147

SCENARIO FAILED: 'Erasure of memory freed by killed userspace processes' (at time 00:28:50)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20660-fix-random-seed-update/3/artifact/build-artifacts/00:28:50_Erasure_of_memory_freed_by_killed_userspace_processes.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20660-fix-random-seed-update/3/artifact/build-artifacts/00:28:50_Erasure_of_memory_freed_by_killed_userspace_processes.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20660-fix-random-seed-update/3/artifact/build-artifacts/00:28:50_Erasure_of_memory_freed_by_killed_userspace_processes.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20660-fix-random-seed-update/3/artifact/build-artifacts/00:28:50_Erasure_of_memory_freed_by_killed_userspace_processes.journal

After features/support/hooks.rb:100 0.000
Tags: @source
5.644
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 5.644
Command failed (returned pid 58094 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20660-fix-random-seed-update/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_20660-fix-random-seed-update/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_20660-fix-random-seed-update/tmp/tails-amd64-20660-fix-random-seed-update@7e4a603f24+stable@874cbb48b2-20241111T1147Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_20660-fix-random-seed-update/tmp/tails-amd64-20660-fix-random-seed-update@7e4a603f24+stable@874cbb48b2-20241111T1147Z.build-manifest
INFO: Need to upgrade to a new APT snapshot:
  - base-files (12.4+deb12u7) to Debian bookworm (12.4+deb12u8)
  - cjson (1.7.15-1+deb12u1) to Debian bookworm (1.7.15-1+deb12u2)
  - curl[curl] (7.88.1-10+deb12u7) to Debian bookworm (7.88.1-10+deb12u8)
  - curl[libcurl4, libcurl3-gnutls] (7.88.1-10+deb12u7) to Debian bookworm (7.88.1-10+deb12u8)
  - distro-info-data (0.58+deb12u2) to Debian bookworm (0.58+deb12u3)
  - glib2.0 (2.74.6-2+deb12u3) to Debian bookworm (2.74.6-2+deb12u4)
  - glibc[libc6, libc-dev-bin, libc-l10n, libc-bin, libc6-dev] (2.36-9+deb12u8) to Debian bookworm (2.36-9+deb12u9)
  - glibc[locales] (2.36-9+deb12u8) to Debian bookworm (2.36-9+deb12u9)
  - gtk+3.0[gtk-update-icon-cache, gir1.2-gtk-3.0] (3.24.38-2~deb12u2) to Debian bookworm (3.24.38-2~deb12u3)
  - gtk+3.0[libgtk-3-0, libgtk-3-common, libgtk-3-bin] (3.24.38-2~deb12u2) to Debian bookworm (3.24.38-2~deb12u3)
  - intel-microcode (3.20240813.1~deb12u1) to Debian bookworm (3.20240910.1~deb12u1)
  - iputils (3:20221126-1) to Debian bookworm (3:20221126-1+deb12u1)
  - ntfs-3g[libntfs-3g89] (1:2022.10.3-1+b1) to Debian bookworm (1:2022.10.3-1+deb12u2)
  - ntfs-3g[ntfs-3g] (1:2022.10.3-1+b1) to Debian bookworm (1:2022.10.3-1+deb12u2)
  - python-cryptography (38.0.4-3) to Debian bookworm (38.0.4-3+deb12u1)
  - sqlite3 (3.40.1-2) to Debian bookworm (3.40.1-2+deb12u1)
  - systemd[libnss-systemd] (252.30-1~deb12u2) to Debian bookworm (252.31-1~deb12u1)
  - systemd[libpam-systemd] (252.30-1~deb12u2) to Debian bookworm (252.31-1~deb12u1)
  - systemd[libudev1, libudev-dev, libsystemd0, libsystemd-shared] (252.30-1~deb12u2) to Debian bookworm (252.31-1~deb12u1)
  - systemd[udev, systemd-sysv, systemd, systemd-timesyncd, systemd-oomd] (252.30-1~deb12u2) to Debian bookworm (252.31-1~deb12u1)
.
<0> expected but was
<#<Process::Status: pid 58094 exit 1>>. (Test::Unit::AssertionFailedError)
/var/lib/jenkins/workspace/test_Tails_ISO_20660-fix-random-seed-update/features/support/helpers/misc_helpers.rb:307:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_20660-fix-random-seed-update/features/support/helpers/misc_helpers.rb:303:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_20660-fix-random-seed-update/features/support/helpers/misc_helpers.rb:303:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_20660-fix-random-seed-update/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.002
After features/support/hooks.rb:100 0.000