Project Number Date
test_Tails_ISO_20979-pdfarranger 8 03 Jun 2025, 03:30

Failures Overview

The following summary displays scenarios that failed.

Feature: Using Tor bridges and pluggable transports
Tags: @product
5:25.238
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.684
And I wait until Tor is ready 4.184
When I disconnect the network through GNOME 2.856
And I connect the network through GNOME 2.803
Then the Tor Connection Assistant autostarts 2.298
And the Tor Connection Assistant connects to Tor 5.894
And I wait until Tor is ready 5:0.517
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.192 
SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:31:56)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20979-pdfarranger/8/artifact/build-artifacts/00:31:56_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20979-pdfarranger/8/artifact/build-artifacts/00:31:56_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_20979-pdfarranger/8/artifact/build-artifacts/00:31:56_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.htpdate
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20979-pdfarranger/8/artifact/build-artifacts/00:31:56_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20979-pdfarranger/8/artifact/build-artifacts/00:31:56_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20979-pdfarranger/8/artifact/build-artifacts/00:31:56_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20979-pdfarranger/8/artifact/build-artifacts/00:31:56_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal
After features/support/hooks.rb:100 0.044
Feature: Additional software
Tags: @product @check_tor_leaks @slow
27:42.879
Scenario I set up Additional Software when installing a package without persistent partition and the package is installed next time I start Tails
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Before features/support/hooks.rb:513 0.006
Steps
Given I start Tails from a freshly installed USB drive with an administration password and the network is plugged and I login 1:49.693
And I update APT using apt 12.988
And I install "popularity-contest" using apt 22.793
Then I am proposed to add the "popularity-contest" package to my Additional Software 8.039
When I create a persistent storage and activate the Additional Software feature 21.219
Then Additional Software is correctly configured for package "popularity-contest" 3.030
When I shutdown Tails and wait for the computer to power off 14.766
And I start Tails from USB drive "__internal" with network unplugged 1:5.296
And I enable persistence 27.177
And I log in to a new session 42.097
And the Additional Software installation service has started 2:15.657
Then I am notified that the installation succeeded 20:0.119
execution 
execution expired (RemoteShell::Timeout)
./features/support/helpers/remote_shell.rb:56:in `read'
./features/support/helpers/remote_shell.rb:56:in `block (3 levels) in communicate'
./features/support/helpers/remote_shell.rb:55:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:42:in `loop'
./features/support/helpers/remote_shell.rb:42:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb:174:in `execute'
./features/support/helpers/remote_shell.rb:185:in `initialize'
./features/support/helpers/dogtail.rb:80:in `new'
./features/support/helpers/dogtail.rb:80:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:595:in `new'
./features/step_definitions/common_steps.rb:595:in `/^I see the "(.+)" notification(?: after at most (\d+) seconds)?$/'
./features/step_definitions/additional_software_packages.rb:28:in `/^I am notified that the installation succeeded$/'
features/additional_software_packages.feature:39:in `Then I am notified that the installation succeeded'
And Additional Software is correctly configured for package "popularity-contest" 0.000
And the package "popularity-contest" is installed after Additional Software has been started 0.000
After features/support/hooks.rb:521 0.042
After features/support/hooks.rb:330 10.903 
SCENARIO FAILED: 'I set up Additional Software when installing a package without persistent partition and the package is installed next time I start Tails' (at time 01:34:06)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20979-pdfarranger/8/artifact/build-artifacts/01:34:06_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20979-pdfarranger/8/artifact/build-artifacts/01:34:06_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20979-pdfarranger/8/artifact/build-artifacts/01:34:06_I_set_up_Additional_Software_when_installing_a_package_without_persistent_partition_and_the_package_is_installed_next_time_I_start_Tails.journal
After features/support/hooks.rb:100 0.009
Feature: Packages are up-to-date
Tags: @source
5.867
Scenario All packages are up-to-date
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:538 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.867
Command 
Command failed (returned pid 52359 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_20979-pdfarranger/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_20979-pdfarranger/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_20979-pdfarranger/tmp/tails-amd64-20979-pdfarranger@29cfd22587+stable@b8835aa720-20250602T2121Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_20979-pdfarranger/tmp/tails-amd64-20979-pdfarranger@29cfd22587+stable@b8835aa720-20250602T2121Z.build-manifest
INFO: Need to upgrade to a new APT snapshot:
  - flatpak (1.14.10-1~deb12u1+tails1) to Debian bookworm-backports (1.16.1-1~bpo12+1)
.
<0> expected but was
<#<Process::Status: pid 52359 exit 1>>. (Test::Unit::AssertionFailedError)
/var/lib/jenkins/workspace/test_Tails_ISO_20979-pdfarranger/features/support/helpers/misc_helpers.rb:307:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_20979-pdfarranger/features/support/helpers/misc_helpers.rb:303:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_20979-pdfarranger/features/support/helpers/misc_helpers.rb:303:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_20979-pdfarranger/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:545 0.000
After features/support/hooks.rb:100 0.000