Project Number Date
test_Tails_ISO_20522-ocr-more 35 20 Jan 2025, 05:08

Failures Overview

The following summary displays scenarios that failed.

Feature: Hardware failures
Tags: @product
36.433
Scenario Outline Alerting about disk read failures before reaching the Welcome Screen
Before features/support/hooks.rb:269 0.005
Steps
Given a computer 0.185
And I start the computer from DVD with network unplugged 36.154
When Tails detects disk read failures on the SquashFS 0.092
Command 
Command failed: systemctl --quiet is-active tails-detect-disk-ioerrors
error code: 3
stdout: 
stderr: .
<false> is not true. (ExecutionFailedInVM)
./features/support/helpers/vm_helper.rb:483:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:480:in `execute_successfully'
./features/step_definitions/hardware.rb:33:in `/^Tails detects disk read failures on the (.+)$/'
features/hardware_failure.feature:14:in `When Tails detects disk read failures on the SquashFS'
features/hardware_failure.feature:10:in `When Tails detects disk read failures on the <device>'
Then I see a disk failure message on the splash screen 0.000
After features/support/hooks.rb:326 4.794 
SCENARIO FAILED: 'Alerting about disk read failures before reaching the Welcome Screen, Examples (#1)' (at time 02:02:53)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/35/artifact/build-artifacts/02:02:53_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___1_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/35/artifact/build-artifacts/02:02:53_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/35/artifact/build-artifacts/02:02:53_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/35/artifact/build-artifacts/02:02:53_Alerting_about_disk_read_failures_before_reaching_the_Welcome_Screen,_Examples___1_.journal
After features/support/hooks.rb:100 0.008
Feature: Hardware failures
Tags: @product @doc
22.060
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:269 0.005
Steps
Given a computer 0.186
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.905
When Tails detects disk read failures on the SquashFS 1.594
Then I see a disk failure message 10.374
FindTextFailed 
FindTextFailed (FindTextFailed)
./features/support/helpers/screen.rb:268:in `rescue in find_text'
./features/support/helpers/screen.rb:261: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.291 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#1)' (at time 02:04:48)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/35/artifact/build-artifacts/02:04:48_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/35/artifact/build-artifacts/02:04:48_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/35/artifact/build-artifacts/02:04:48_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/35/artifact/build-artifacts/02:04:48_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.journal
After features/support/hooks.rb:100 0.000
Feature: Hardware failures
Tags: @product @doc
22.967
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:269 0.005
Steps
Given a computer 0.231
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.606
When Tails detects disk read failures on the boot device 1.890
Then I see a disk failure message 10.239
FindTextFailed 
FindTextFailed (FindTextFailed)
./features/support/helpers/screen.rb:268:in `rescue in find_text'
./features/support/helpers/screen.rb:261: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.138 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#2)' (at time 02:05:16)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/35/artifact/build-artifacts/02:05:16_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/35/artifact/build-artifacts/02:05:16_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/35/artifact/build-artifacts/02:05:16_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/35/artifact/build-artifacts/02:05:16_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.877
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:269 0.003
Steps
Given a computer 0.197
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.560
When Tails detects disk read failures on the boot device with a target error 1.857
Then I see a disk failure message 10.261
FindTextFailed 
FindTextFailed (FindTextFailed)
./features/support/helpers/screen.rb:268:in `rescue in find_text'
./features/support/helpers/screen.rb:261: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.236 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#3)' (at time 02:05:44)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/35/artifact/build-artifacts/02:05:44_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/35/artifact/build-artifacts/02:05:44_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/35/artifact/build-artifacts/02:05:44_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/35/artifact/build-artifacts/02:05:44_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
5.837
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.837
Command 
Command failed (returned pid 64004 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@77e50ff1b9+stable@abccafff95-20250119T2357Z.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@77e50ff1b9+stable@abccafff95-20250119T2357Z.build-manifest
INFO: Need to upgrade to a new APT snapshot:
  - libreoffice (4:102.12+LibO7.4.7-1+deb12u6) to Debian bookworm-backports (4:24.8.4-1~bpo12+1)
.
<0> expected but was
<#<Process::Status: pid 64004 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: Tor stream isolation is effective
Tags: @product @check_tor_leaks
3:20.084
Scenario The Tor Browser is using the web browser-specific SocksPort
Steps
When I monitor the network connections of Tor Browser 0.067
And I start the Tor Browser 19.946
And the Tor Browser loads the startup page 3:0.069
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/browser.rb:200:in `page_has_loaded_in_the_tor_browser'
./features/step_definitions/browser.rb:495:in `/^the Tor Browser loads the (startup page|Tails homepage|Tails GitLab)$/'
features/tor_stream_isolation.feature:30:in `And the Tor Browser loads the startup page'
Then I see that Tor Browser is properly stream isolated 0.000
After features/support/hooks.rb:515 0.029
After features/support/hooks.rb:326 5.463 
SCENARIO FAILED: 'The Tor Browser is using the web browser-specific SocksPort' (at time 04:02:57)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/35/artifact/build-artifacts/04:02:57_The_Tor_Browser_is_using_the_web_browser-specific_SocksPort.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/35/artifact/build-artifacts/04:02:57_The_Tor_Browser_is_using_the_web_browser-specific_SocksPort.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/35/artifact/build-artifacts/04:02:57_The_Tor_Browser_is_using_the_web_browser-specific_SocksPort.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/35/artifact/build-artifacts/04:02:57_The_Tor_Browser_is_using_the_web_browser-specific_SocksPort.journal
After features/support/hooks.rb:100 0.000