Project Number Date
test_Tails_ISO_test-suite-early-boot-hooks 4 09 Dec 2024, 20:22

Failures Overview

The following summary displays scenarios that failed.

Feature: Using Tor bridges and pluggable transports
Tags: @product
5:22.324
Scenario The same Tor configuration is applied when the network is reconnected
Steps
Given I configure a direct connection in the Tor Connection Assistant 8.309
And I wait until Tor is ready 2.162
When I disconnect the network through GNOME 3.271
And I connect the network through GNOME 2.822
Then the Tor Connection Assistant autostarts 2.134
And the Tor Connection Assistant connects to Tor 3.384
And I wait until Tor is ready 5:0.239
Time 
Time syncing failed (HtpdateError)
./features/step_definitions/common_steps.rb:711:in `rescue in block in <top (required)>'
./features/step_definitions/common_steps.rb:709:in `/^the time has synced$/'
./features/step_definitions/common_steps.rb:662: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:330 5.332 
SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:31:14)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-early-boot-hooks/4/artifact/build-artifacts/00:31:14_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-early-boot-hooks/4/artifact/build-artifacts/00:31:14_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_test-suite-early-boot-hooks/4/artifact/build-artifacts/00:31:14_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.htpdate
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-early-boot-hooks/4/artifact/build-artifacts/00:31:14_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-early-boot-hooks/4/artifact/build-artifacts/00:31:14_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-early-boot-hooks/4/artifact/build-artifacts/00:31:14_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-early-boot-hooks/4/artifact/build-artifacts/00:31:14_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal
After features/support/hooks.rb:100 0.054
Feature: Packages are up-to-date
Tags: @source
12.386
Scenario All packages are up-to-date
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:536 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 12.386
Command 
Command failed (returned pid 54716 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_test-suite-early-boot-hooks/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_test-suite-early-boot-hooks/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_test-suite-early-boot-hooks/tmp/tails-amd64-test-suite-early-boot-hooks@2ef19c7552+stable@4704781f33-20241209T1435Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_test-suite-early-boot-hooks/tmp/tails-amd64-test-suite-early-boot-hooks@2ef19c7552+stable@4704781f33-20241209T1435Z.build-manifest
INFO: Need to upgrade to a new APT snapshot:
  - blinker (1.8.2-1) to Debian trixie (1.9.0-1)
  - firmware-sof (2024.06-2) to Debian trixie (2024.09.1-1)
  - flask (3.0.3-1) to Debian trixie (3.1.0-2)
  - python-werkzeug (3.0.4-1) to Debian trixie (3.1.3-2)
.
<0> expected but was
<#<Process::Status: pid 54716 exit 1>>. (Test::Unit::AssertionFailedError)
/var/lib/jenkins/workspace/test_Tails_ISO_test-suite-early-boot-hooks/features/support/helpers/misc_helpers.rb:307:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_test-suite-early-boot-hooks/features/support/helpers/misc_helpers.rb:303:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_test-suite-early-boot-hooks/features/support/helpers/misc_helpers.rb:303:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_test-suite-early-boot-hooks/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:543 0.000
After features/support/hooks.rb:100 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
3:34.999
Scenario The Tor Browser cannot access the LAN
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD and logged in and the network is connected 12.482
And a web server is running on the LAN 1.047
And I capture all network traffic 0.008
When I start the Tor Browser 21.438
And the Tor Browser loads the startup page 3:0.022
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:200:in `page_has_loaded_in_the_tor_browser'
./features/step_definitions/browser.rb:495:in `/^the Tor Browser loads the (startup page|Tails homepage|Tails GitLab)$/'
features/torified_browsing.feature:12:in `And the Tor Browser loads the startup page'
And I open a page on the LAN web server in the Tor Browser 0.000
Then the Tor Browser shows the "Unable to connect" error 0.000
And no traffic was sent to the web server on the LAN 0.000
After features/support/hooks.rb:330 5.253 
SCENARIO FAILED: 'The Tor Browser cannot access the LAN' (at time 04:18:43)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-early-boot-hooks/4/artifact/build-artifacts/04:18:43_The_Tor_Browser_cannot_access_the_LAN.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-early-boot-hooks/4/artifact/build-artifacts/04:18:43_The_Tor_Browser_cannot_access_the_LAN.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-early-boot-hooks/4/artifact/build-artifacts/04:18:43_The_Tor_Browser_cannot_access_the_LAN.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_test-suite-early-boot-hooks/4/artifact/build-artifacts/04:18:43_The_Tor_Browser_cannot_access_the_LAN.journal
After features/support/hooks.rb:100 0.052