Project Number Date
test_Tails_ISO_stable 5628 06 May 2025, 19:37

Failures Overview

The following summary displays scenarios that failed.

Feature: Using Tor bridges and pluggable transports
Tags: @product
5:54.726
Scenario The same Tor configuration is applied when the network is reconnected
Steps
Given I configure a direct connection in the Tor Connection Assistant 10.014
And I wait until Tor is ready 29.903
When I disconnect the network through GNOME 2.960
And I connect the network through GNOME 2.974
Then the Tor Connection Assistant autostarts 2.320
And the Tor Connection Assistant connects to Tor 6.273
And I wait until Tor is ready 5:0.278
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.421 
SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:32:37)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5628/artifact/build-artifacts/00:32:37_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5628/artifact/build-artifacts/00:32:37_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_stable/5628/artifact/build-artifacts/00:32:37_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.htpdate
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5628/artifact/build-artifacts/00:32:37_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5628/artifact/build-artifacts/00:32:37_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5628/artifact/build-artifacts/00:32:37_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5628/artifact/build-artifacts/00:32:37_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal
After features/support/hooks.rb:100 0.050
Feature: Hardware failures
Tags: @product
2:59.486
Scenario Outline Disk partitioning errors without a persistent partition
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given a computer 0.238
And I set Tails to boot with options "test_partitioning_errors=guid" 0.000
And I temporarily create a 7200 MiB disk named "temp" 0.051
And I plug USB drive "temp" 1.057
And I write the Tails USB image to disk "temp" 33.475
When I start Tails from USB drive "temp" with network unplugged 2:24.662
try_for() 
try_for() timeout expired
Last ignored exception was: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/tmp/gdm-env'
./features/support/helpers/remote_shell.rb:71: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/usb.rb:108:in `new'
./features/step_definitions/usb.rb:108:in `greeter'
./features/step_definitions/common_steps.rb:460: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/common_steps.rb:459:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:284: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/common_steps.rb:459:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:284: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/hardware_failure.feature:80:in `When I start Tails from USB drive "temp" with network unplugged'
features/hardware_failure.feature:72:in `When I start Tails from USB drive "temp" with network unplugged'
Then Tails is running from USB drive "temp" 0.000
And the Greeter recommends reinstalling Tails due to partitioning errors 0.000
And the Greeter forbids starting Tails 0.000
And the Greeter forbids all settings but language 0.000
And Tails detected partitioning error guid-not-randomized 0.000
After features/support/hooks.rb:330 4.979 
SCENARIO FAILED: 'Disk partitioning errors without a persistent partition, Examples (#1)' (at time 02:35:36)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5628/artifact/build-artifacts/02:35:36_Disk_partitioning_errors_without_a_persistent_partition,_Examples___1_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5628/artifact/build-artifacts/02:35:36_Disk_partitioning_errors_without_a_persistent_partition,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5628/artifact/build-artifacts/02:35:36_Disk_partitioning_errors_without_a_persistent_partition,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5628/artifact/build-artifacts/02:35:36_Disk_partitioning_errors_without_a_persistent_partition,_Examples___1_.journal
After features/support/hooks.rb:100 0.146
Feature: Packages are up-to-date
Tags: @source
20.566
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 20.566
Command 
Command failed (returned pid 55642 exit 1): ["/var/lib/jenkins/workspace/test_Tails_ISO_stable/bin/needed-package-updates", "--config=/var/lib/jenkins/workspace/test_Tails_ISO_stable/config/ci/needed-package-updates.yml", "--file=/var/lib/jenkins/workspace/test_Tails_ISO_stable/tmp/tails-amd64-stable@c19e815cbe-20250506T1335Z.build-manifest", {:err=>[:child, :out]}]:
INFO: Check local file /var/lib/jenkins/workspace/test_Tails_ISO_stable/tmp/tails-amd64-stable@c19e815cbe-20250506T1335Z.build-manifest
INFO: Need to upgrade to a new APT snapshot:
  - firmware-free (20241210-1) to Debian trixie (20241210-2)
  - firmware-nonfree[firmware-libertas, firmware-brcm80211, firmware-atheros, firmware-amd-graphics, firmware-intel-graphics, firmware-intel-misc, firmware-iwlwifi, firmware-ipw2x00, firmware-intel-sound] (20241210-1) to Debian trixie (20250410-2)
  - firmware-nonfree[firmware-ti-connectivity, firmware-mediatek, firmware-realtek, firmware-linux-nonfree, firmware-nvidia-graphics, firmware-linux, firmware-misc-nonfree] (20241210-1) to Debian trixie (20250410-2)
.
<0> expected but was
<#<Process::Status: pid 55642 exit 1>>. (Test::Unit::AssertionFailedError)
/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/support/helpers/misc_helpers.rb:307:in `block in cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/support/helpers/misc_helpers.rb:303:in `popen'
/var/lib/jenkins/workspace/test_Tails_ISO_stable/features/support/helpers/misc_helpers.rb:303:in `cmd_helper'
/var/lib/jenkins/workspace/test_Tails_ISO_stable/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: Using persistent Tor bridges and pluggable transports
4:35.720
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Steps
Given I have started Tails without network from a USB drive without a persistent partition and logged in 13.340
And I create a persistent partition with the default settings 23.112
Then the "TorConfiguration" tps feature is not enabled 2.772
When the network is plugged 0.081
And the Tor Connection Assistant autostarts 8.518
And I configure some persistent obfs4 bridges in the Tor Connection Assistant 11.812
And I wait until Tor is ready 3.291
Then tca.conf includes the configured bridges 0.019
And the "TorConfiguration" tps feature is enabled and active 1.307
When I cold reboot the computer 10.024
And the computer reboots Tails 1:12.888
And I enable persistence 31.422
And I capture all network traffic 0.008
And I log in to a new session 36.646
Then tca.conf includes the configured bridges 0.016
When the network is plugged 0.456
And the Tor Connection Assistant autostarts 1:0.001
TCA 
TCA did not start (TorBootstrapFailure)
./features/step_definitions/tor.rb:375:in `rescue in block in <top (required)>'
./features/step_definitions/tor.rb:371:in `/^the Tor Connection Assistant (?:autostarts|is running)$/'
features/persistent_tor_bridges.feature:24:in `And the Tor Connection Assistant autostarts'
Feature: Using persistent Tor bridges and pluggable transports
Tags: @product
0.000
Scenario Disabling persistence of Tor bridges
Steps
When I choose to connect to Tor automatically 0.000
And I accept Tor Connection's offer to use my persistent bridges 0.000
And I disable saving bridges to Persistent Storage 0.000
And I configure a direct connection in the Tor Connection Assistant 0.000
Then I wait until Tor is ready 0.000
And tca.conf includes no bridge 0.000
And the "TorConfiguration" tps feature is not enabled and not active 0.000
And all Internet traffic has only flowed through Tor or connectivity check service 0.000
After features/support/hooks.rb:330 14.324 
SCENARIO FAILED: 'Disabling persistence of Tor bridges' (at time 04:19:27)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5628/artifact/build-artifacts/04:19:27_Disabling_persistence_of_Tor_bridges_chutney-data
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5628/artifact/build-artifacts/04:19:27_Disabling_persistence_of_Tor_bridges.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5628/artifact/build-artifacts/04:19:27_Disabling_persistence_of_Tor_bridges.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/5628/artifact/build-artifacts/04:19:27_Disabling_persistence_of_Tor_bridges.journal
After features/support/hooks.rb:100 0.053