Project Number Date
test_Tails_ISO_20531-early-reporting-of-bad-devices 2 06 Dec 2024, 01:10

Failures Overview

The following summary displays scenarios that failed.

Tags: @product
2:26.015
Scenario Error when the GPT backup header is corrupt
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.002
Steps
Given a computer 0.226
And I set Tails to boot with options "test_gpt_corruption=gpt_backup,gpt_backup_table" 0.000
And I create a 7200 MiB disk named "temp" 0.043
And I plug USB drive "temp" 1.050
And I write the Tails USB image to disk "temp" 29.764
And I start Tails from USB drive "temp" with network unplugged 1:30.124
Then Tails is running from USB drive "temp" 0.364
When I log in to a new session 16.619
And all notifications have disappeared 7.578
Then the system journal includes message "Detected partitioning-corruption, but not showing any message" 0.242
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/common_steps.rb:1739:in `/^the system journal includes message "([^"]+)"$/'
features/usb_install.feature:119:in `Then the system journal includes message "Detected partitioning-corruption, but not showing any message"'
After features/support/hooks.rb:330 4.870

SCENARIO FAILED: 'Error when the GPT backup header is corrupt' (at time 01:03:35)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20531-early-reporting-of-bad-devices/2/artifact/build-artifacts/01:03:35_Error_when_the_GPT_backup_header_is_corrupt.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20531-early-reporting-of-bad-devices/2/artifact/build-artifacts/01:03:35_Error_when_the_GPT_backup_header_is_corrupt.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20531-early-reporting-of-bad-devices/2/artifact/build-artifacts/01:03:35_Error_when_the_GPT_backup_header_is_corrupt.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20531-early-reporting-of-bad-devices/2/artifact/build-artifacts/01:03:35_Error_when_the_GPT_backup_header_is_corrupt.journal

After features/support/hooks.rb:100 0.006
Tags: @product
2:7.695
Scenario Error when the disk GUID has not changed
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given a computer 0.192
And I set Tails to boot with options "test_gpt_corruption=guid" 0.000
And I create a 7200 MiB disk named "temp" 0.170
And I plug USB drive "temp" 1.045
And I write the Tails USB image to disk "temp" 27.544
And I start Tails from USB drive "temp" with network unplugged 1:23.104
Then Tails is running from USB drive "temp" 0.366
When I log in to a new session 15.272
can
can not find any of the patterns ["TailsGreeterLoginButton.png", "TailsGreeterLoginButtonGerman.png"] on the screen (FindFailed)
./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:497:in `/^I log in to a new session(?: in ([^ ]*) \(([^ ]*)\))?( without activating the Persistent Storage)?( after having activated the Persistent Storage| expecting no warning about the Persistent Storage not being activated)?$/'
features/usb_install.feature:129:in `When I log in to a new session'
And all notifications have disappeared 0.000
Then I see an error about system partition resizing 0.000
After features/support/hooks.rb:330 5.153

SCENARIO FAILED: 'Error when the disk GUID has not changed' (at time 01:05:48)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20531-early-reporting-of-bad-devices/2/artifact/build-artifacts/01:05:48_Error_when_the_disk_GUID_has_not_changed.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20531-early-reporting-of-bad-devices/2/artifact/build-artifacts/01:05:48_Error_when_the_disk_GUID_has_not_changed.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20531-early-reporting-of-bad-devices/2/artifact/build-artifacts/01:05:48_Error_when_the_disk_GUID_has_not_changed.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20531-early-reporting-of-bad-devices/2/artifact/build-artifacts/01:05:48_Error_when_the_disk_GUID_has_not_changed.journal

After features/support/hooks.rb:100 0.007
Tags: @source
12.879
Scenario All packages are up-to-date
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:536 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 12.879
Command failed (returned pid 58131 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20531-early-reporting-of-bad-devices/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_20531-early-reporting-of-bad-devices/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_20531-early-reporting-of-bad-devices/tmp/tails-amd64-20531-early-reporting-of-bad-devices@25f4c2d364+stable@24ab794c74-20241205T1941Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_20531-early-reporting-of-bad-devices/tmp/tails-amd64-20531-early-reporting-of-bad-devices@25f4c2d364+stable@24ab794c74-20241205T1941Z.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)
  - flask (3.0.3-1) to Debian trixie (3.1.0-2)
  - python-werkzeug (3.0.4-1) to Debian trixie (3.1.3-2)
.
<0> expected but was
<#<Process::Status: pid 58131 exit 1>>. (Test::Unit::AssertionFailedError)
/var/lib/jenkins/workspace/test_Tails_ISO_20531-early-reporting-of-bad-devices/features/support/helpers/misc_helpers.rb:307:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_20531-early-reporting-of-bad-devices/features/support/helpers/misc_helpers.rb:303:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_20531-early-reporting-of-bad-devices/features/support/helpers/misc_helpers.rb:303:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_20531-early-reporting-of-bad-devices/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:543 0.000
After features/support/hooks.rb:100 0.000