Project Number Date
test_Tails_ISO_18215-update-chutney-force-all-tests 11 27 Mar 2025, 19:49

Failures Overview

The following summary displays scenarios that failed.

Tags: @product
5:25.914
Scenario The same Tor configuration is applied when the network is reconnected
Steps
Given I configure a direct connection in the Tor Connection Assistant 7.587
And I wait until Tor is ready 3.459
When I disconnect the network through GNOME 2.667
And I connect the network through GNOME 3.107
Then the Tor Connection Assistant autostarts 2.533
And the Tor Connection Assistant connects to Tor 6.245
And I wait until Tor is ready 5:0.313
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.444

SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:31:49)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_18215-update-chutney-force-all-tests/11/artifact/build-artifacts/00:31:49_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected_chutney-data

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_18215-update-chutney-force-all-tests/11/artifact/build-artifacts/00:31:49_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_18215-update-chutney-force-all-tests/11/artifact/build-artifacts/00:31:49_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.htpdate

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_18215-update-chutney-force-all-tests/11/artifact/build-artifacts/00:31:49_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png

Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_18215-update-chutney-force-all-tests/11/artifact/build-artifacts/00:31:49_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.tor

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_18215-update-chutney-force-all-tests/11/artifact/build-artifacts/00:31:49_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_18215-update-chutney-force-all-tests/11/artifact/build-artifacts/00:31:49_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal

After features/support/hooks.rb:100 0.046
Tags: @source
5.605
Scenario All packages are up-to-date
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:530 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.604
Command failed (pid 56240 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_18215-update-chutney-force-all-tests/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_18215-update-chutney-force-all-tests/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_18215-update-chutney-force-all-tests/tmp/tails-amd64-18215-update-chutney+force-all-tests@a4cf545420+stable@ac80093f6d-20250327T1311Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_18215-update-chutney-force-all-tests/tmp/tails-amd64-18215-update-chutney+force-all-tests@a4cf545420+stable@ac80093f6d-20250327T1311Z.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:
  - ghostscript (10.0.0~dfsg-11+deb12u6) to Debian bookworm-security (10.0.0~dfsg-11+deb12u7)
 (CommandFailed)
/var/lib/jenkins/workspace/test_Tails_ISO_18215-update-chutney-force-all-tests/features/support/helpers/misc_helpers.rb:321:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_18215-update-chutney-force-all-tests/features/support/helpers/misc_helpers.rb:314:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_18215-update-chutney-force-all-tests/features/support/helpers/misc_helpers.rb:314:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_18215-update-chutney-force-all-tests/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:537 0.000
After features/support/hooks.rb:100 0.000
Tags: @product
22:44.896
Scenario Creating and using a persistent NetworkManager connection
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 enabled and logged in 9.756
And the network is plugged 0.074
And Tor is ready 19.901
And I add a wired DHCP NetworkManager connection called "persistent-con-current" 0.216
And I shutdown Tails and wait for the computer to power off 8.697
Given I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 22:6.249
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:719:in `new'
./features/step_definitions/common_steps.rb:719:in `/^all notifications have disappeared$/'
./features/step_definitions/common_steps.rb:298:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/persistence.feature:88:in `Given I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
And I capture all network traffic 0.000
And the network is plugged 0.000
And Tor is ready 0.000
And I switch to the "persistent-con-current" NetworkManager connection 0.000
And the 1st network device has a spoofed MAC address configured 0.000
And no network device leaked the real MAC address 0.000
After features/support/hooks.rb:330 10.823

SCENARIO FAILED: 'Creating and using a persistent NetworkManager connection' (at time 03:59:18)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_18215-update-chutney-force-all-tests/11/artifact/build-artifacts/03:59:18_Creating_and_using_a_persistent_NetworkManager_connection.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_18215-update-chutney-force-all-tests/11/artifact/build-artifacts/03:59:18_Creating_and_using_a_persistent_NetworkManager_connection.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_18215-update-chutney-force-all-tests/11/artifact/build-artifacts/03:59:18_Creating_and_using_a_persistent_NetworkManager_connection.journal

After features/support/hooks.rb:100 0.010