Project Number Date
test_Tails_ISO_20522-ocr-more 21 30 Dec 2024, 05:05

Failures Overview

The following summary displays scenarios that failed.

Feature: Tails documentation
Tags: @product @doc @not_release_blocker
51.627
Scenario The Tails documentation launcher works when offline
Before features/support/hooks.rb:269 0.007
Steps
Given I have started Tails from DVD without network and logged in 9.803
When I start "Tails Documentation" via GNOME Activities Overview 10.708
Then the Tor Browser has started 31.115
cannot 
cannot find TorBrowserNewTabButton.png on the screen (FindFailed)
./features/support/helpers/screen.rb:179:in `rescue in wait'
./features/support/helpers/screen.rb:163:in `wait'
./features/step_definitions/browser.rb:465:in `/^the Tor Browser (?:has started|starts)$/'
features/documentation.feature:7:in `Then the Tor Browser has started'
Then "Tails - Documentation" has loaded in the Tor Browser 0.000
After features/support/hooks.rb:326 6.173 
SCENARIO FAILED: 'The Tails documentation launcher works when offline' (at time 01:59:39)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/21/artifact/build-artifacts/01:59:39_The_Tails_documentation_launcher_works_when_offline.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/21/artifact/build-artifacts/01:59:39_The_Tails_documentation_launcher_works_when_offline.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/21/artifact/build-artifacts/01:59:39_The_Tails_documentation_launcher_works_when_offline.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/21/artifact/build-artifacts/01:59:39_The_Tails_documentation_launcher_works_when_offline.journal
After features/support/hooks.rb:100 0.000
Feature: Hardware failures
Tags: @product @doc
19.572
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:269 0.005
Steps
Given a computer 0.271
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.797
When Tails detects disk read failures on the SquashFS 0.501
Then I see a disk failure message 10.001
try_for() 
try_for() timeout expired
Last ignored exception was: FindTextFailed: FindTextFailed
./features/support/helpers/screen.rb:263:in `block in find_text'
./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/support/helpers/screen.rb:262:in `find_text'
./features/step_definitions/hardware.rb:42: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/support/helpers/screen.rb:262:in `find_text'
./features/step_definitions/hardware.rb:42:in `/^I see a disk failure message$/'
features/hardware_failure.feature:27:in `Then I see a disk failure message'
features/hardware_failure.feature:23:in `Then I see a disk failure message'
Then I can open the hardware failure documentation from the disk failure message 0.000
After features/support/hooks.rb:326 5.427 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#1)' (at time 02:10:15)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/21/artifact/build-artifacts/02:10:15_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/21/artifact/build-artifacts/02:10:15_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/21/artifact/build-artifacts/02:10:15_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/21/artifact/build-artifacts/02:10:15_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.journal
After features/support/hooks.rb:100 0.000
Feature: Hardware failures
Tags: @product @doc
20.912
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:269 0.006
Steps
Given a computer 0.232
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.111
When Tails detects disk read failures on the boot device 1.561
Then I see a disk failure message 10.006
try_for() 
try_for() timeout expired
Last ignored exception was: FindTextFailed: FindTextFailed
./features/support/helpers/screen.rb:263:in `block in find_text'
./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/support/helpers/screen.rb:262:in `find_text'
./features/step_definitions/hardware.rb:42: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/support/helpers/screen.rb:262:in `find_text'
./features/step_definitions/hardware.rb:42:in `/^I see a disk failure message$/'
features/hardware_failure.feature:28:in `Then I see a disk failure message'
features/hardware_failure.feature:23:in `Then I see a disk failure message'
Then I can open the hardware failure documentation from the disk failure message 0.000
After features/support/hooks.rb:326 5.654 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#2)' (at time 02:10:42)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/21/artifact/build-artifacts/02:10:42_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/21/artifact/build-artifacts/02:10:42_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/21/artifact/build-artifacts/02:10:42_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/21/artifact/build-artifacts/02:10:42_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.journal
After features/support/hooks.rb:100 0.000
Feature: Hardware failures
Tags: @product @doc
22.111
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:269 0.004
Steps
Given a computer 0.290
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.975
When Tails detects disk read failures on the boot device with a target error 1.804
Then I see a disk failure message 10.040
try_for() 
try_for() timeout expired
Last ignored exception was: FindTextFailed: FindTextFailed
./features/support/helpers/screen.rb:263:in `block in find_text'
./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/support/helpers/screen.rb:262:in `find_text'
./features/step_definitions/hardware.rb:42: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/support/helpers/screen.rb:262:in `find_text'
./features/step_definitions/hardware.rb:42:in `/^I see a disk failure message$/'
features/hardware_failure.feature:29:in `Then I see a disk failure message'
features/hardware_failure.feature:23:in `Then I see a disk failure message'
Then I can open the hardware failure documentation from the disk failure message 0.000
After features/support/hooks.rb:326 5.997 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#3)' (at time 02:11:10)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/21/artifact/build-artifacts/02:11:10_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/21/artifact/build-artifacts/02:11:10_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/21/artifact/build-artifacts/02:11:10_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/21/artifact/build-artifacts/02:11:10_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.journal
After features/support/hooks.rb:100 0.000
Feature: Packages are up-to-date
Tags: @source
6.036
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.036
Command 
Command failed (returned pid 57442 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20522-ocr-more/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_20522-ocr-more/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_20522-ocr-more/tmp/tails-amd64-20522-ocr-more@f80a34a36d+stable@05d403c596-20241229T2357Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_20522-ocr-more/tmp/tails-amd64-20522-ocr-more@f80a34a36d+stable@05d403c596-20241229T2357Z.build-manifest
INFO: Need to upgrade to a new APT snapshot:
  - firmware-free (20240610-1) to Debian trixie (20241210-1)
  - firmware-nonfree[firmware-ipw2x00, firmware-atheros, firmware-intel-graphics, firmware-intel-sound, firmware-brcm80211, firmware-intel-misc, firmware-amd-graphics, firmware-libertas, firmware-iwlwifi] (20240909-2) to Debian trixie (20241210-1)
  - firmware-nonfree[firmware-nvidia-graphics, firmware-mediatek, firmware-realtek, firmware-linux, firmware-misc-nonfree, firmware-linux-nonfree] (20240909-2) to Debian trixie (20241210-1)
  - firmware-nonfree[firmware-ti-connectivity] (20240909-2) to Debian trixie (20241210-1)
  - firmware-sof (2024.06-2) to Debian trixie (2024.09.2-1)
.
<0> expected but was
<#<Process::Status: pid 57442 exit 1>>. (Test::Unit::AssertionFailedError)
/var/lib/jenkins/workspace/test_Tails_ISO_20522-ocr-more/features/support/helpers/misc_helpers.rb:307:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_20522-ocr-more/features/support/helpers/misc_helpers.rb:303:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_20522-ocr-more/features/support/helpers/misc_helpers.rb:303:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_20522-ocr-more/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
Feature: Tails persistence
Tags: @product @doc
1:17.323
Scenario Filesystem and I/O errors
Before features/support/hooks.rb:269 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 9.302
And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 5.616
And Tails detects disk read failures on the boot device 1.507
When I try to enable persistence 0.501
Then the Welcome Screen tells me that my hardware is probably failing 5.059
When I log in to a new session 21.774
And all notifications have disappeared 6.068
Then the Tor Browser starts 27.492
cannot 
cannot find TorBrowserNewTabButton.png on the screen (FindFailed)
./features/support/helpers/screen.rb:179:in `rescue in wait'
./features/support/helpers/screen.rb:163:in `wait'
./features/step_definitions/browser.rb:465:in `/^the Tor Browser (?:has started|starts)$/'
features/persistence.feature:213:in `Then the Tor Browser starts'
And "Tails - Recovering data from the Persistent Storage when it has file system errors" has loaded in the Tor Browser 0.000
After features/support/hooks.rb:326 6.725 
SCENARIO FAILED: 'Filesystem and I/O errors' (at time 03:32:22)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/21/artifact/build-artifacts/03:32:22_Filesystem_and_I_O_errors.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/21/artifact/build-artifacts/03:32:22_Filesystem_and_I_O_errors.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/21/artifact/build-artifacts/03:32:22_Filesystem_and_I_O_errors.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/21/artifact/build-artifacts/03:32:22_Filesystem_and_I_O_errors.journal
After features/support/hooks.rb:100 0.000