Project Number Date
test_Tails_ISO_20522-ocr-more 22 31 Dec 2024, 05:10

Failures Overview

The following summary displays scenarios that failed.

Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker
12:56.649
Scenario Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online
Before features/support/hooks.rb:269 0.006
Before features/support/hooks.rb:507 0.007
Steps
Given a computer 0.190
And I start Tails from USB drive "__internal" and I login with persistence enabled and an administration password 2:11.804
And I configure APT to prefer an old version of cowsay 0.025
When I install an old version "3.03+dfsg2-1" of the cowsay package using apt 25.237
And I accept adding "cowsay" to Additional Software 5.333
And Additional Software is correctly configured for package "cowsay" 0.868
And I shutdown Tails and wait for the computer to power off 6.344
And I start Tails from USB drive "__internal" with network unplugged 1:9.692
And I enable persistence 15.477
# We need to add back this custom APT source for the Additional Software
# install step, as it was not saved in persistence
And I configure APT to prefer an old version of cowsay 0.025
# Prevent the "Warning: virtual machine detected!" notification from racing
# with the one we'll be interacting with below.
And I disable the tails-virt-notify-user.service user unit 0.088
And I log in to a new session 28.887
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 30.934
And I revert the APT tweaks that made it prefer an old version of cowsay 0.069
# We remove the newest package after it has been downloaded and before
# it is installed, so that the upgrade process fails
And I prepare the Additional Software upgrade process to fail 0.068
And the network is plugged 0.072
And Tor is ready 26.798
And available upgrades have been checked 1.132
And I see the "The upgrade of your additional software failed" notification after at most 300 seconds 3.703
And I can open the Additional Software configuration window from the notification 3.513
And I shutdown Tails and wait for the computer to power off 2:6.775
And I start Tails from USB drive "__internal" with network unplugged 1:2.458
And I enable persistence 14.808
# We need to add back this custom APT source for the Additional Software
# install step, as it was not saved in persistence
And I configure APT to prefer an old version of cowsay 0.031
And I log in to a new session 27.853
And the installed version of package "cowsay" is "3.03+dfsg2-1" after Additional Software has been started 2:12.698
And I revert the APT tweaks that made it prefer an old version of cowsay 0.062
And the network is plugged 0.071
And Tor is ready 1:1.621
TCA 
TCA did not start (TorBootstrapFailure)
./features/step_definitions/tor.rb:375:in `rescue in block in <top (required)>'
./features/step_definitions/tor.rb:371:in `/^the Tor Connection Assistant (?:autostarts|is running)$/'
./features/step_definitions/common_steps.rb:645:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:600:in `/^Tor is ready$/'
features/additional_software_packages.feature:114:in `And Tor is ready'
Then the Additional Software upgrade service has started 0.000
And the installed version of package "cowsay" is newer than "3.03+dfsg2-1" 0.000
After features/support/hooks.rb:515 0.052
After features/support/hooks.rb:326 14.269 
SCENARIO FAILED: 'Recovering in offline mode after Additional Software previously failed to upgrade and then succeed to upgrade when online' (at time 01:31:06)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/22/artifact/build-artifacts/01:31:06_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online_chutney-data
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/22/artifact/build-artifacts/01:31:06_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/22/artifact/build-artifacts/01:31:06_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/22/artifact/build-artifacts/01:31:06_Recovering_in_offline_mode_after_Additional_Software_previously_failed_to_upgrade_and_then_succeed_to_upgrade_when_online.journal
After features/support/hooks.rb:100 0.034
Feature: Hardware failures
Tags: @product @doc
35.407
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:269 0.006
Steps
Given a computer 0.242
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 24.761
When Tails detects disk read failures on the SquashFS 0.401
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.293 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#1)' (at time 02:15:17)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/22/artifact/build-artifacts/02:15:17_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/22/artifact/build-artifacts/02:15:17_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/22/artifact/build-artifacts/02:15:17_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/22/artifact/build-artifacts/02:15:17_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.journal
After features/support/hooks.rb:100 0.000
Feature: Hardware failures
Tags: @product @doc
21.577
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:269 0.011
Steps
Given a computer 0.201
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.322
When Tails detects disk read failures on the boot device 1.926
Then I see a disk failure message 10.126
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.969 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#2)' (at time 02:15:44)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/22/artifact/build-artifacts/02:15:44_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/22/artifact/build-artifacts/02:15:44_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/22/artifact/build-artifacts/02:15:44_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/22/artifact/build-artifacts/02:15:44_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.journal
After features/support/hooks.rb:100 0.000
Feature: Hardware failures
Tags: @product @doc
20.642
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:269 0.006
Steps
Given a computer 0.177
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.716
When Tails detects disk read failures on the boot device with a target error 0.746
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: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.795 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#3)' (at time 02:16:11)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/22/artifact/build-artifacts/02:16:11_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/22/artifact/build-artifacts/02:16:11_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/22/artifact/build-artifacts/02:16:11_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/22/artifact/build-artifacts/02:16:11_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.journal
After features/support/hooks.rb:100 0.000
Feature: Localization
Tags: @product @doc @slow @not_release_blocker
2:3.474
Scenario Outline Tails is localized for every tier-1 language
Before features/support/hooks.rb:269 0.006
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.298
When I log in to a new session in Chinese (zh_CN) 36.062
Then the keyboard layout is set to "cn" 0.423
When the network is plugged 0.102
And Tor is ready 21.968
Then I successfully start the Unsafe Browser in "zh_CN" 18.665
And I kill the Unsafe Browser 5.852
When I enable the screen keyboard 0.175
Then the screen keyboard works in Tor Browser 28.575
And DuckDuckGo is the default search engine 3.352
undefined 
undefined method `child' for nil:NilClass

           .child(roleName: 'entry')
           ^^^^^^ (NoMethodError)
./features/step_definitions/browser.rb:27:in `browser_url_entry'
./features/step_definitions/browser.rb:36:in `set_browser_url'
./features/step_definitions/browser.rb:393:in `/^DuckDuckGo is the default search engine$/'
features/localization.feature:45:in `And DuckDuckGo is the default search engine'
features/localization.feature:31:in `And DuckDuckGo is the default search engine'
And I kill the Tor Browser 0.000
And the screen keyboard works in Thunderbird 0.000
And the layout of the screen keyboard is set to "us" 0.000
After features/support/hooks.rb:326 6.237 
SCENARIO FAILED: 'Tails is localized for every tier-1 language, Examples (#2)' (at time 02:26:59)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/22/artifact/build-artifacts/02:26:59_Tails_is_localized_for_every_tier-1_language,_Examples___2_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/22/artifact/build-artifacts/02:26:59_Tails_is_localized_for_every_tier-1_language,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/22/artifact/build-artifacts/02:26:59_Tails_is_localized_for_every_tier-1_language,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/22/artifact/build-artifacts/02:26:59_Tails_is_localized_for_every_tier-1_language,_Examples___2_.journal
After features/support/hooks.rb:100 0.000
Feature: Packages are up-to-date
Tags: @source
5.859
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.859
Command 
Command failed (returned pid 54548 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-20241230T2357Z.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-20241230T2357Z.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-iwlwifi, firmware-intel-misc, firmware-brcm80211, firmware-intel-sound, firmware-atheros, firmware-libertas, firmware-amd-graphics, firmware-intel-graphics] (20240909-2) to Debian trixie (20241210-1)
  - firmware-nonfree[firmware-nvidia-graphics, firmware-linux-nonfree, firmware-misc-nonfree, firmware-mediatek, firmware-realtek, firmware-linux] (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 54548 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: Browsing the web using the Tor Browser
Tags: @product
1:37.466
Scenario The persistent Tor Browser directory is usable
Before features/support/hooks.rb:269 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.028
And the network is plugged 0.148
And I successfully configure Tor 19.870
And available upgrades have been checked 0.075
And all notifications have disappeared 4.411
Then the persistent Tor Browser directory exists 0.054
And there is a GNOME bookmark for the persistent Tor Browser directory 1.693
When I start the Tor Browser 26.287
And I open the address "https://tails.net/about" in the Tor Browser 16.599
And "Tails - How Tails works" has loaded in the Tor Browser 1.223
Then I can save the current page as "index.html" to the persistent Tor Browser GNOME bookmark 16.073
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: Error: atspi_error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (1)
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:346:in `call_tree_node_method'
./features/support/helpers/dogtail.rb:358:in `block in grabFocus'
./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/dogtail.rb:357:in `grabFocus'
./features/step_definitions/browser.rb:554: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/dogtail.rb:357:in `grabFocus'
./features/step_definitions/browser.rb:554:in `/^I (can|cannot) save the current page as "([^"]+[.]html)" to the (.*) (directory|GNOME bookmark)$/'
features/torified_browsing.feature:129:in `Then I can save the current page as "index.html" to the persistent Tor Browser GNOME bookmark'
And I open the address "file:///home/amnesia/Persistent/Tor Browser/index.html" in the Tor Browser 0.000
Then "Tails - How Tails works" has loaded in the Tor Browser 0.000
And I can print the current page as "output.pdf" to the persistent Tor Browser directory 0.000
After features/support/hooks.rb:326 6.424 
SCENARIO FAILED: 'The persistent Tor Browser directory is usable' (at time 04:14:37)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/22/artifact/build-artifacts/04:14:37_The_persistent_Tor_Browser_directory_is_usable.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/22/artifact/build-artifacts/04:14:37_The_persistent_Tor_Browser_directory_is_usable.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/22/artifact/build-artifacts/04:14:37_The_persistent_Tor_Browser_directory_is_usable.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/22/artifact/build-artifacts/04:14:37_The_persistent_Tor_Browser_directory_is_usable.journal
After features/support/hooks.rb:100 0.000