Project Number Date
test_Tails_ISO_20522-ocr-more 46 30 Jan 2025, 16:01

Failures Overview

The following summary displays scenarios that failed.

Feature: Time syncing
Tags: @product @check_tor_leaks @not_release_blocker
2:8.500
Scenario The system time is not synced to the hardware clock
Before features/support/hooks.rb:269 0.002
Before features/support/hooks.rb:507 0.002
Steps
Given I have started Tails from DVD without network and logged in 15.649
When I bump the system time with "-15 days" 0.384
And I warm reboot the computer 0.019
And the computer reboots Tails 1:52.447
try_for() 
try_for() timeout expired
Last ignored exception was: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/tmp/gdm-env'
./features/support/helpers/remote_shell.rb:71:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:42:in `loop'
./features/support/helpers/remote_shell.rb:42:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb:174:in `execute'
./features/support/helpers/remote_shell.rb:185:in `initialize'
./features/support/helpers/dogtail.rb:80:in `new'
./features/support/helpers/dogtail.rb:80:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/usb.rb:108:in `new'
./features/step_definitions/usb.rb:108:in `greeter'
./features/step_definitions/common_steps.rb:451:in `block (2 levels) in <top (required)>'
./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/step_definitions/common_steps.rb:450: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/step_definitions/common_steps.rb:450:in `/^the computer (?:re)?boots Tails$/'
features/time_syncing.feature:37:in `And the computer reboots Tails'
Then Tails' hardware clock is close to the host system's time 0.000
After features/support/hooks.rb:515 0.049
After features/support/hooks.rb:326 4.909 
SCENARIO FAILED: 'The system time is not synced to the hardware clock' (at time 00:14:12)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/46/artifact/build-artifacts/00:14:12_The_system_time_is_not_synced_to_the_hardware_clock.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/46/artifact/build-artifacts/00:14:12_The_system_time_is_not_synced_to_the_hardware_clock.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/46/artifact/build-artifacts/00:14:12_The_system_time_is_not_synced_to_the_hardware_clock.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/46/artifact/build-artifacts/00:14:12_The_system_time_is_not_synced_to_the_hardware_clock.journal
After features/support/hooks.rb:100 0.005
Feature: Hardware failures
Tags: @product @doc
19.981
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:269 0.004
Steps
Given a computer 0.180
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.413
When Tails detects disk read failures on the SquashFS 0.350
Then I see a disk failure message 10.037
undefined 
undefined local variable or method `language' for #<Screen:0x00007f1185e3c720 @w=1024, @h=768, @_assertion_wrapped=false>

    debug_log("Could not find text, here is full ocr:\n#{ocr(language:)}")
                                                             ^^^^^^^^^ (NameError)
./features/support/helpers/screen.rb:267:in `rescue in wait_text'
./features/support/helpers/screen.rb:261:in `wait_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.278 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#1)' (at time 02:09:26)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/46/artifact/build-artifacts/02:09:26_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/46/artifact/build-artifacts/02:09:26_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/46/artifact/build-artifacts/02:09:26_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/46/artifact/build-artifacts/02:09:26_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.859
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:269 0.005
Steps
Given a computer 0.248
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.889
When Tails detects disk read failures on the boot device 0.617
Then I see a disk failure message 10.104
undefined 
undefined local variable or method `language' for #<Screen:0x00007f1182293048 @w=1024, @h=768, @_assertion_wrapped=false>

    debug_log("Could not find text, here is full ocr:\n#{ocr(language:)}")
                                                             ^^^^^^^^^ (NameError)
./features/support/helpers/screen.rb:267:in `rescue in wait_text'
./features/support/helpers/screen.rb:261:in `wait_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.262 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#2)' (at time 02:09:52)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/46/artifact/build-artifacts/02:09:52_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/46/artifact/build-artifacts/02:09:52_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/46/artifact/build-artifacts/02:09:52_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/46/artifact/build-artifacts/02:09:52_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.journal
After features/support/hooks.rb:100 0.000
Feature: Hardware failures
Tags: @product @doc
21.938
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:269 0.005
Steps
Given a computer 0.180
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.902
When Tails detects disk read failures on the boot device with a target error 1.741
Then I see a disk failure message 10.114
undefined 
undefined local variable or method `language' for #<Screen:0x00007f1182430108 @w=1024, @h=768, @_assertion_wrapped=false>

    debug_log("Could not find text, here is full ocr:\n#{ocr(language:)}")
                                                             ^^^^^^^^^ (NameError)
./features/support/helpers/screen.rb:267:in `rescue in wait_text'
./features/support/helpers/screen.rb:261:in `wait_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.232 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#3)' (at time 02:10:20)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/46/artifact/build-artifacts/02:10:20_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/46/artifact/build-artifacts/02:10:20_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/46/artifact/build-artifacts/02:10:20_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/46/artifact/build-artifacts/02:10:20_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
10.380
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 10.380
Command 
Command failed (returned pid 60237 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@101d8e77c1+stable@7733074f62-20250130T1016Z.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@101d8e77c1+stable@7733074f62-20250130T1016Z.build-manifest
INFO: Need to upgrade to a new APT snapshot:
  - zd1211-firmware (1:1.5-12) to Debian trixie (1:1.5-13)
.
<0> expected but was
<#<Process::Status: pid 60237 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