Project Number Date
test_Tails_ISO_20522-ocr-more 26 04 Jan 2025, 05:15

Failures Overview

The following summary displays scenarios that failed.

Feature: Using Tor bridges and pluggable transports
Tags: @product
5:25.606
Scenario The same Tor configuration is applied when the network is reconnected
Steps
Given I configure a direct connection in the Tor Connection Assistant 6.428
And I wait until Tor is ready 4.053
When I disconnect the network through GNOME 3.144
And I connect the network through GNOME 2.887
Then the Tor Connection Assistant autostarts 2.236
And the Tor Connection Assistant connects to Tor 6.479
And I wait until Tor is ready 5:0.378
Time 
Time syncing failed (HtpdateError)
./features/step_definitions/common_steps.rb:704:in `rescue in block in <top (required)>'
./features/step_definitions/common_steps.rb:702:in `/^the time has synced$/'
./features/step_definitions/common_steps.rb:655:in `/^I wait until Tor is ready$/'
features/tor_bridges.feature:89:in `And I wait until Tor is ready'
And Tor is using the same configuration as before 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through Tor or connectivity check service 0.000
After features/support/hooks.rb:326 5.281 
SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:32:25)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/26/artifact/build-artifacts/00:32:25_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/26/artifact/build-artifacts/00:32:25_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.file_content_var_log_boot.log
Htpdate logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/26/artifact/build-artifacts/00:32:25_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.htpdate
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/26/artifact/build-artifacts/00:32:25_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/26/artifact/build-artifacts/00:32:25_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/26/artifact/build-artifacts/00:32:25_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/26/artifact/build-artifacts/00:32:25_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal
After features/support/hooks.rb:100 0.040
Feature: GNOME is well-integrated into Tails
Tags: @product
4:19.342
Scenario I can launch various apps via GNOME Activities Overview
Before features/support/hooks.rb:269 0.006
Steps
# Some apps (Electrum and Persistent Storage Backup) only start when
# a Persistent Storage is available.
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.662
# Some apps (Tor Browser) only start when the network is plugged.
And the network is plugged 0.088
And Tor is ready 19.130
And all notifications have disappeared 4.236
When I start "Additional Software" via GNOME Activities Overview 10.626
And I close the "tails-additional-software-config" window 2.263
When I start "Disks" via GNOME Activities Overview 8.121
# The close button of GNOME Disks is not accessible
And I close the "gnome-disks" window via Alt+F4 1.631
When I start "GNOME Terminal" via GNOME Activities Overview 8.827
And I close the "gnome-terminal-server" window 1.899
When I start "Files" via GNOME Activities Overview 8.124
And I close the "org.gnome.Nautilus" window 16.990
When I start "Persistent Storage" via GNOME Activities Overview 10.190
And I close the "tps-frontend" window 4.029
When I start "Persistent Storage Backup" via GNOME Activities Overview 10.616
And I close the "zenity" window 2.364
When I start "Pidgin" via GNOME Activities Overview 8.314
And I close the "Pidgin" window via Alt+F4 6.788
When I start "Thunderbird" via GNOME Activities Overview 8.887
And I close the "Thunderbird" window 13.728
When I start "Tor Browser" via GNOME Activities Overview 9.560
And I close the "Firefox" window 20.852
When I start "Unlock VeraCrypt Volumes" via GNOME Activities Overview 12.405
And I close the "unlock-veracrypt-volumes" window 1:0.001
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: child of [desktop frame | main]: "unlock-veracrypt-volumes" application
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:1156:in `new'
./features/step_definitions/common_steps.rb:1156: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:1155: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:1155:in `/^I close the "([^"]+)" window$/'
features/gnome.feature:47:in `And I close the "unlock-veracrypt-volumes" window'
When I start "Unsafe Browser" via GNOME Activities Overview 0.000
And I close the "Firefox" window 0.000
After features/support/hooks.rb:326 6.446 
SCENARIO FAILED: 'I can launch various apps via GNOME Activities Overview' (at time 02:15:17)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/26/artifact/build-artifacts/02:15:17_I_can_launch_various_apps_via_GNOME_Activities_Overview.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/26/artifact/build-artifacts/02:15:17_I_can_launch_various_apps_via_GNOME_Activities_Overview.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/26/artifact/build-artifacts/02:15:17_I_can_launch_various_apps_via_GNOME_Activities_Overview.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/26/artifact/build-artifacts/02:15:17_I_can_launch_various_apps_via_GNOME_Activities_Overview.journal
After features/support/hooks.rb:100 0.000
Feature: Hardware failures
Tags: @product @doc
20.222
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:269 0.004
Steps
Given a computer 0.189
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.353
When Tails detects disk read failures on the SquashFS 0.678
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 6.323 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#1)' (at time 02:18:01)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/26/artifact/build-artifacts/02:18:01_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/26/artifact/build-artifacts/02:18:01_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/26/artifact/build-artifacts/02:18:01_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/26/artifact/build-artifacts/02:18:01_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.995
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:269 0.006
Steps
Given a computer 0.266
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.790
When Tails detects disk read failures on the boot device 1.850
Then I see a disk failure message 10.087
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.571 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#2)' (at time 02:18:29)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/26/artifact/build-artifacts/02:18:29_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/26/artifact/build-artifacts/02:18:29_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/26/artifact/build-artifacts/02:18:29_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/26/artifact/build-artifacts/02:18:29_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.596
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:269 0.007
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 9.503
When Tails detects disk read failures on the boot device with a target error 1.834
Then I see a disk failure message 10.060
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.635 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#3)' (at time 02:18:56)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/26/artifact/build-artifacts/02:18:56_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/26/artifact/build-artifacts/02:18:56_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/26/artifact/build-artifacts/02:18:56_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20522-ocr-more/26/artifact/build-artifacts/02:18:56_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.735
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.735
Command 
Command failed (returned pid 59417 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-20250103T2357Z.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-20250103T2357Z.build-manifest
INFO: Need to upgrade to a new APT snapshot:
  - firmware-free (20240610-1) to Debian trixie (20241210-1)
  - firmware-nonfree[firmware-amd-graphics, firmware-atheros, firmware-intel-misc, firmware-iwlwifi, firmware-ipw2x00, firmware-brcm80211, firmware-intel-sound, firmware-libertas, firmware-intel-graphics] (20240909-2) to Debian trixie (20241210-1)
  - firmware-nonfree[firmware-mediatek, firmware-linux, firmware-linux-nonfree, firmware-misc-nonfree, firmware-realtek, firmware-nvidia-graphics] (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 59417 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