Project Number Date
test_Tails_ISO_10422-tor-browser-in-flatpak 19 14 Feb 2025, 17:34

Failures Overview

The following summary displays scenarios that failed.

Feature: Using Tor bridges and pluggable transports
Tags: @product
40.594
Scenario Using obfs4 pluggable transports from a QR code
Steps
When I configure some obfs4 bridges from a QR code in the Tor Connection Assistant in hide mode 40.594
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/tor.rb:663:in `block (2 levels) in <top (required)>'
./features/step_definitions/tor.rb:499:in `tca_configure'
./features/step_definitions/tor.rb:626:in `/^I configure (?:some|the) (persistent )?(\w+) bridges (from a QR code )?in the Tor Connection Assistant(?: in (easy|hide) mode)?( without connecting|)$/'
features/tor_bridges.feature:28:in `When I configure some obfs4 bridges from a QR code in the Tor Connection Assistant in hide mode'
Then I wait until Tor is ready 0.000
And tca.conf includes the configured bridges 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through the configured bridges 0.000
After features/support/hooks.rb:326 5.977 
SCENARIO FAILED: 'Using obfs4 pluggable transports from a QR code' (at time 00:22:16)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/19/artifact/build-artifacts/00:22:16_Using_obfs4_pluggable_transports_from_a_QR_code.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/19/artifact/build-artifacts/00:22:16_Using_obfs4_pluggable_transports_from_a_QR_code.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/19/artifact/build-artifacts/00:22:16_Using_obfs4_pluggable_transports_from_a_QR_code.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/19/artifact/build-artifacts/00:22:16_Using_obfs4_pluggable_transports_from_a_QR_code.journal
After features/support/hooks.rb:100 0.053
Feature: Using Tor bridges and pluggable transports
Tags: @product
1:9.826
Scenario TCA can scan QR code after a connection failure
Steps
Given the Tor network and default bridges are blocked 2.031
When I unsuccessfully configure a direct connection in the Tor Connection Assistant 30.832
Then the Tor Connection Assistant reports that it failed to connect 0.125
And tca.conf is empty 0.234
Given I scan a QR code from the error page in Tor Connection Assistant 36.602
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/tor.rb:737:in `/^I scan a QR code from the error page in Tor Connection Assistant$/'
features/tor_bridges.feature:39:in `Given I scan a QR code from the error page in Tor Connection Assistant'
And I retry connecting to Tor 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes the configured bridges 0.000
And available upgrades have been checked 0.000
And all Internet traffic has only flowed through the configured bridges or connectivity check service 0.000
After features/support/hooks.rb:326 6.010 
SCENARIO FAILED: 'TCA can scan QR code after a connection failure' (at time 00:23:46)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/19/artifact/build-artifacts/00:23:46_TCA_can_scan_QR_code_after_a_connection_failure.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/19/artifact/build-artifacts/00:23:46_TCA_can_scan_QR_code_after_a_connection_failure.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/19/artifact/build-artifacts/00:23:46_TCA_can_scan_QR_code_after_a_connection_failure.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/19/artifact/build-artifacts/00:23:46_TCA_can_scan_QR_code_after_a_connection_failure.journal
After features/support/hooks.rb:100 0.037
Feature: Additional software
Tags: @product @check_tor_leaks @slow @not_release_blocker_inherited
2:57.086
Scenario I am notified when Additional Software fails to install a package
Before features/support/hooks.rb:269 0.004
Before features/support/hooks.rb:507 0.004
Steps
Given a computer 0.216
And I start Tails from USB drive "__internal" with network unplugged 59.844
And I enable persistence 13.341
And I remove the "cowsay" deb files from the APT cache 0.078
# 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.112
And I log in to a new session 38.676
Then I see the "The installation of your additional software failed" notification after at most 300 seconds 4.137
And I can open the Additional Software log file from the notification 1:0.680
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.549 
SCENARIO FAILED: 'I am notified when Additional Software fails to install a package' (at time 01:27:56)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/19/artifact/build-artifacts/01:27:56_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/19/artifact/build-artifacts/01:27:56_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/19/artifact/build-artifacts/01:27:56_I_am_notified_when_Additional_Software_fails_to_install_a_package.journal
After features/support/hooks.rb:100 0.008
Feature: Packages are up-to-date
Tags: @source
6.151
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 6.151
Command 
Command failed (returned pid 55658 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@7157583399+stable@c1c411a585-20250214T1157Z.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@7157583399+stable@c1c411a585-20250214T1157Z.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 55658 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