Project Number Date
test_Tails_ISO_10422-tor-browser-in-flatpak 17 14 Feb 2025, 16:09

Failures Overview

The following summary displays scenarios that failed.

Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited
3:15.029
Scenario I am notified when Additional Software fails to install a package
Before features/support/hooks.rb:269 0.006
Before features/support/hooks.rb:507 0.006
Steps
Given a computer 0.304
And I start Tails from USB drive "__internal" with network unplugged 1:4.671
And I enable persistence 13.630
And I remove the "cowsay" deb files from the APT cache 0.093
# 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.138
And I log in to a new session 42.030
Then I see the "The installation of your additional software failed" notification after at most 300 seconds 13.273
And I can open the Additional Software log file from the notification 1:0.887
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: child of [desktop frame | main]: "gnome-text-editor" application
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/additional_software_packages.rb:171:in `new'
./features/step_definitions/additional_software_packages.rb:171: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/additional_software_packages.rb:170: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/additional_software_packages.rb:170:in `/^I can open the Additional Software log file from the notification$/'
features/additional_software_packages.feature:130:in `And I can open the Additional Software log file from the notification'
And the package "cowsay" is not installed 0.000
After features/support/hooks.rb:515 0.036
After features/support/hooks.rb:326 8.714 
SCENARIO FAILED: 'I am notified when Additional Software fails to install a package' (at time 01:32:49)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/17/artifact/build-artifacts/01:32:49_I_am_notified_when_Additional_Software_fails_to_install_a_package.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/17/artifact/build-artifacts/01:32:49_I_am_notified_when_Additional_Software_fails_to_install_a_package.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/17/artifact/build-artifacts/01:32:49_I_am_notified_when_Additional_Software_fails_to_install_a_package.journal
After features/support/hooks.rb:100 0.009
Feature: Tails documentation
Tags: @product @doc @not_release_blocker
3:43.389
Scenario The Tails documentation launcher works when offline
Before features/support/hooks.rb:269 0.006
Steps
Given I have started Tails from DVD without network and logged in 8.608
When I start "Tails Documentation" via GNOME Activities Overview 10.877
Then the Tor Browser has started 23.821
Then "Tails - Documentation" has loaded in the Tor Browser 3:0.081
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:208:in `page_has_loaded_in_the_tor_browser'
./features/step_definitions/browser.rb:223:in `/^"([^"]+)" has loaded in the Tor Browser$/'
features/documentation.feature:8:in `Then "Tails - Documentation" has loaded in the Tor Browser'
After features/support/hooks.rb:326 5.988 
SCENARIO FAILED: 'The Tails documentation launcher works when offline' (at time 02:07:03)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/17/artifact/build-artifacts/02:07:03_The_Tails_documentation_launcher_works_when_offline.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/17/artifact/build-artifacts/02:07:03_The_Tails_documentation_launcher_works_when_offline.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/17/artifact/build-artifacts/02:07:03_The_Tails_documentation_launcher_works_when_offline.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/17/artifact/build-artifacts/02:07:03_The_Tails_documentation_launcher_works_when_offline.journal
After features/support/hooks.rb:100 0.000
Feature: Hardware failures
Tags: @product @doc
3:30.202
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:269 0.005
Steps
Given a computer 0.172
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.710
When Tails detects disk read failures on the SquashFS 0.407
Then I see a disk failure message 2.770
Then I can open the hardware failure documentation from the disk failure message 3:17.141
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:208:in `page_has_loaded_in_the_tor_browser'
./features/step_definitions/browser.rb:223:in `/^"([^"]+)" has loaded in the Tor Browser$/'
./features/step_definitions/hardware.rb:52:in `/^I can open the hardware failure documentation from the disk failure message$/'
features/hardware_failure.feature:27:in `Then I can open the hardware failure documentation from the disk failure message'
features/hardware_failure.feature:24:in `Then I can open the hardware failure documentation from the disk failure message'
After features/support/hooks.rb:326 7.324 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#1)' (at time 02:20:20)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/17/artifact/build-artifacts/02:20:20_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_10422-tor-browser-in-flatpak/17/artifact/build-artifacts/02:20:20_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/17/artifact/build-artifacts/02:20:20_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/17/artifact/build-artifacts/02:20:20_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.journal
After features/support/hooks.rb:100 0.000
Feature: Hardware failures
Tags: @product @doc
3:30.804
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:269 0.005
Steps
Given a computer 0.952
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.141
When Tails detects disk read failures on the boot device 1.770
Then I see a disk failure message 1.271
Then I can open the hardware failure documentation from the disk failure message 3:16.669
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:208:in `page_has_loaded_in_the_tor_browser'
./features/step_definitions/browser.rb:223:in `/^"([^"]+)" has loaded in the Tor Browser$/'
./features/step_definitions/hardware.rb:52:in `/^I can open the hardware failure documentation from the disk failure message$/'
features/hardware_failure.feature:28:in `Then I can open the hardware failure documentation from the disk failure message'
features/hardware_failure.feature:24:in `Then I can open the hardware failure documentation from the disk failure message'
After features/support/hooks.rb:326 7.117 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#2)' (at time 02:23:58)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/17/artifact/build-artifacts/02:23:58_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_10422-tor-browser-in-flatpak/17/artifact/build-artifacts/02:23:58_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/17/artifact/build-artifacts/02:23:58_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/17/artifact/build-artifacts/02:23:58_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.journal
After features/support/hooks.rb:100 0.000
Feature: Hardware failures
Tags: @product @doc
3:34.547
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:269 0.006
Steps
Given a computer 0.226
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 9.508
When Tails detects disk read failures on the boot device with a target error 0.558
Then I see a disk failure message 3.381
Then I can open the hardware failure documentation from the disk failure message 3:20.872
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:208:in `page_has_loaded_in_the_tor_browser'
./features/step_definitions/browser.rb:223:in `/^"([^"]+)" has loaded in the Tor Browser$/'
./features/step_definitions/hardware.rb:52:in `/^I can open the hardware failure documentation from the disk failure message$/'
features/hardware_failure.feature:29:in `Then I can open the hardware failure documentation from the disk failure message'
features/hardware_failure.feature:24:in `Then I can open the hardware failure documentation from the disk failure message'
After features/support/hooks.rb:326 8.060 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#3)' (at time 02:27:40)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/17/artifact/build-artifacts/02:27:40_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/17/artifact/build-artifacts/02:27:40_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/17/artifact/build-artifacts/02:27:40_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
7.842
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 7.842
Command 
Command failed (returned pid 56256 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_10422-tor-browser-in-flatpak/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_10422-tor-browser-in-flatpak/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_10422-tor-browser-in-flatpak/tmp/tails-amd64-10422-tor-browser-in-flatpak@5f8f616cff+stable@c1c411a585-20250214T1007Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_10422-tor-browser-in-flatpak/tmp/tails-amd64-10422-tor-browser-in-flatpak@5f8f616cff+stable@c1c411a585-20250214T1007Z.build-manifest
INFO: Need to upgrade to a new APT snapshot:
  - flatpak (1.14.10-1+deb12u1+tails1) to Debian trixie (1.16.0-1)
  - onionshare (2.6.2-1~0.tails1) to Debian sid (2.6.2-5)
.
<0> expected but was
<#<Process::Status: pid 56256 exit 1>>. (Test::Unit::AssertionFailedError)
/var/lib/jenkins/workspace/test_Tails_ISO_10422-tor-browser-in-flatpak/features/support/helpers/misc_helpers.rb:307:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_10422-tor-browser-in-flatpak/features/support/helpers/misc_helpers.rb:303:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_10422-tor-browser-in-flatpak/features/support/helpers/misc_helpers.rb:303:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_10422-tor-browser-in-flatpak/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
4:49.896
Scenario Manual filesystem repair fails
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 8.425
And the Persistent Storage filesystem is corrupted beyond what e2fsck can repair 0.121
When I try to enable persistence 0.294
Then the Welcome Screen tells me that filesystem errors were found on the Persistent Storage 34.612
When I repair the filesystem of the Persistent Storage 1.345
Then the Welcome Screen tells me that it failed to repair the Persistent Storage 0.140
When I log in to a new session 39.142
And all notifications have disappeared 9.892
# Now both WhisperBack and Tor Browser has started at the same
# time, so we do not know which window is focused. The steps about
# Tor Browser care about that, but the ones about WhisperBack do
# not, so we first deal with WhisperBack and then kill it to
# ensure that Tor Browser is focused.
Then WhisperBack is prefilled for fsck with summary: "Failed to repair the file system of your Persistent Storage" 0.270
And the file "/var/lib/gdm3/post-greeter-whisperback.json" is empty 1.045
When I close the "whisperback" window 1.695
Then the Tor Browser starts 12.811
And "Tails - Recovering data from the Persistent Storage when it has file system errors" has loaded in the Tor Browser 3:0.097
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:208:in `page_has_loaded_in_the_tor_browser'
./features/step_definitions/browser.rb:223:in `/^"([^"]+)" has loaded in the Tor Browser$/'
features/persistence.feature:202:in `And "Tails - Recovering data from the Persistent Storage when it has file system errors" has loaded in the Tor Browser'
After features/support/hooks.rb:326 6.106 
SCENARIO FAILED: 'Manual filesystem repair fails' (at time 04:04:01)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/17/artifact/build-artifacts/04:04:01_Manual_filesystem_repair_fails.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/17/artifact/build-artifacts/04:04:01_Manual_filesystem_repair_fails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/17/artifact/build-artifacts/04:04:01_Manual_filesystem_repair_fails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/17/artifact/build-artifacts/04:04:01_Manual_filesystem_repair_fails.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product @doc
5:5.380
Scenario Filesystem and I/O errors
Before features/support/hooks.rb:269 0.006
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 8.818
And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 22.086
And Tails detects disk read failures on the boot device 1.611
When I try to enable persistence 0.437
Then the Welcome Screen tells me that my hardware is probably failing 17.938
When I log in to a new session 49.537
And all notifications have disappeared 8.254
Then the Tor Browser starts 16.620
And "Tails - Recovering data from the Persistent Storage when it has file system errors" has loaded in the Tor Browser 3:0.076
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:208:in `page_has_loaded_in_the_tor_browser'
./features/step_definitions/browser.rb:223:in `/^"([^"]+)" has loaded in the Tor Browser$/'
features/persistence.feature:214:in `And "Tails - Recovering data from the Persistent Storage when it has file system errors" has loaded in the Tor Browser'
After features/support/hooks.rb:326 6.947 
SCENARIO FAILED: 'Filesystem and I/O errors' (at time 04:09:13)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/17/artifact/build-artifacts/04:09:13_Filesystem_and_I_O_errors.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/17/artifact/build-artifacts/04:09:13_Filesystem_and_I_O_errors.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/17/artifact/build-artifacts/04:09:13_Filesystem_and_I_O_errors.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/17/artifact/build-artifacts/04:09:13_Filesystem_and_I_O_errors.journal
After features/support/hooks.rb:100 0.000
Feature: Various checks for torified software
Tags: @product @check_tor_leaks
1:40.072
Scenario wget(1) should work for HTTPS and go through Tor
Steps
When I wget "https://example.com/" to stdout 1:40.072
Tor 
Tor operation failed (despite retrying 10 times) with
RuntimeError: wget:ing https://example.com/ with options  failed with:

--2025-02-14 15:48:05--  https://example.com/
Resolving example.com (example.com)... 23.192.228.84
Connecting to example.com (example.com)|23.192.228.84|:443... connected.
GnuTLS: A TLS fatal alert has been received.
GnuTLS: received alert [80]: Internal error
Unable to establish SSL connection.
 (MaxRetriesFailure)
./features/support/helpers/misc_helpers.rb:226:in `rescue in block in retry_action'
./features/support/helpers/misc_helpers.rb:209:in `block in retry_action'
./features/support/helpers/misc_helpers.rb:208:in `loop'
./features/support/helpers/misc_helpers.rb:208:in `retry_action'
./features/support/helpers/misc_helpers.rb:196:in `retry_tor'
./features/step_definitions/torified_misc.rb:4:in `/^I (wget|curl) "([^"]+)" to stdout(?:| with the '([^']+)' options)$/'
features/torified_misc.feature:8:in `When I wget "https://example.com/" to stdout'
Then the wget command is successful 0.000
And the wget standard output contains "Example Domain" 0.000
After features/support/hooks.rb:515 0.058
After features/support/hooks.rb:326 5.320 
SCENARIO FAILED: 'wget(1) should work for HTTPS and go through Tor' (at time 04:57:23)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/17/artifact/build-artifacts/04:57:23_wget_1__should_work_for_HTTPS_and_go_through_Tor.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/17/artifact/build-artifacts/04:57:23_wget_1__should_work_for_HTTPS_and_go_through_Tor.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/17/artifact/build-artifacts/04:57:23_wget_1__should_work_for_HTTPS_and_go_through_Tor.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/17/artifact/build-artifacts/04:57:23_wget_1__should_work_for_HTTPS_and_go_through_Tor.journal
After features/support/hooks.rb:100 0.000
Feature: Various checks for torified software
Tags: @product @check_tor_leaks
1:40.025
Scenario curl should work for HTTPS and go through Tor
Steps
When I curl "https://example.com/" to stdout 1:40.025
Tor 
Tor operation failed (despite retrying 10 times) with
RuntimeError: curl:ing https://example.com/ with options  failed with:

 (MaxRetriesFailure)
./features/support/helpers/misc_helpers.rb:226:in `rescue in block in retry_action'
./features/support/helpers/misc_helpers.rb:209:in `block in retry_action'
./features/support/helpers/misc_helpers.rb:208:in `loop'
./features/support/helpers/misc_helpers.rb:208:in `retry_action'
./features/support/helpers/misc_helpers.rb:196:in `retry_tor'
./features/step_definitions/torified_misc.rb:4:in `/^I (wget|curl) "([^"]+)" to stdout(?:| with the '([^']+)' options)$/'
features/torified_misc.feature:17:in `When I curl "https://example.com/" to stdout'
Then the curl command is successful 0.000
And the curl standard output contains "Example Domain" 0.000
After features/support/hooks.rb:515 0.036
After features/support/hooks.rb:326 5.230 
SCENARIO FAILED: 'curl should work for HTTPS and go through Tor' (at time 04:59:36)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/17/artifact/build-artifacts/04:59:36_curl_should_work_for_HTTPS_and_go_through_Tor.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/17/artifact/build-artifacts/04:59:36_curl_should_work_for_HTTPS_and_go_through_Tor.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/17/artifact/build-artifacts/04:59:36_curl_should_work_for_HTTPS_and_go_through_Tor.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/17/artifact/build-artifacts/04:59:36_curl_should_work_for_HTTPS_and_go_through_Tor.journal
After features/support/hooks.rb:100 0.000