Project Number Date
test_Tails_ISO_10422-tor-browser-in-flatpak 30 11 Mar 2025, 21:09

Failures Overview

The following summary displays scenarios that failed.

Feature: Using Tor bridges and pluggable transports
Tags: @product
5:24.872
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.583
And I wait until Tor is ready 2.905
When I disconnect the network through GNOME 2.862
And I connect the network through GNOME 2.911
Then the Tor Connection Assistant autostarts 2.259
And the Tor Connection Assistant connects to Tor 6.552
And I wait until Tor is ready 5:0.797
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.207 
SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:30:58)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/30/artifact/build-artifacts/00:30:58_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/30/artifact/build-artifacts/00:30:58_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_10422-tor-browser-in-flatpak/30/artifact/build-artifacts/00:30:58_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.htpdate
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/30/artifact/build-artifacts/00:30:58_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/30/artifact/build-artifacts/00:30:58_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/30/artifact/build-artifacts/00:30:58_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/30/artifact/build-artifacts/00:30:58_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal
After features/support/hooks.rb:100 0.040
Feature: Packages are up-to-date
Tags: @source
10.397
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 10.397
Command 
Command failed (returned pid 67092 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@1b234841a5+stable@b47406be20-20250311T1432Z.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@1b234841a5+stable@b47406be20-20250311T1432Z.build-manifest
ERROR: tor-geoipdb: the package version(0.4.8.14-1+tpo1~d12.bookworm+1) is higher than the version on experimental (0.4.8.14-1)
ERROR: tor: the package version(0.4.8.14-1+tpo1~d12.bookworm+1) is higher than the version on experimental (0.4.8.14-1)
INFO: Need to upgrade to a new APT snapshot:
  - flatpak (1.14.10-1+deb12u1+tails1) to Debian trixie (1.16.0-1)
.
<0> expected but was
<#<Process::Status: pid 67092 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:543 0.000
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product
4:35.364
Scenario Persistent Greeter options
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails without network from a USB drive with a persistent partition and stopped at Tails Greeter's login screen 12.636
When I enable persistence 38.711
Then no persistent Greeter options were restored 14.625
When I set all Greeter options to non-default values 30.370
And I log in to a new session in German (de) after having activated the Persistent Storage 43.544
Then all Greeter options are set to non-default values 0.395
When I cold reboot the computer 7.744
And the computer reboots Tails 1:17.266
Given I enable persistence 50.069
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/usb.rb:694:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:704:in `/^I enable persistence( with the changed passphrase)?$/'
features/persistence.feature:111:in `Given I enable persistence'
Then persistent Greeter options were restored 0.000
When I log in to a new session after having activated the Persistent Storage 0.000
Then all Greeter options are set to non-default values 0.000
After features/support/hooks.rb:330 6.978 
SCENARIO FAILED: 'Persistent Greeter options' (at time 03:38:45)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/30/artifact/build-artifacts/03:38:45_Persistent_Greeter_options.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/30/artifact/build-artifacts/03:38:45_Persistent_Greeter_options.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/30/artifact/build-artifacts/03:38:45_Persistent_Greeter_options.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_10422-tor-browser-in-flatpak/30/artifact/build-artifacts/03:38:45_Persistent_Greeter_options.journal
After features/support/hooks.rb:100 0.014