Project Number Date
test_Tails_ISO_tca-misc-improvements 1 09 Apr 2025, 15:51

Failures Overview

The following summary displays scenarios that failed.

Feature: Using Tor bridges and pluggable transports
Tags: @product
5:29.396
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.204
And I wait until Tor is ready 6.695
When I disconnect the network through GNOME 2.791
And I connect the network through GNOME 3.012
Then the Tor Connection Assistant autostarts 2.546
And the Tor Connection Assistant connects to Tor 6.399
And I wait until Tor is ready 5:0.746
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.267 
SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:32:03)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_tca-misc-improvements/1/artifact/build-artifacts/00:32:03_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_tca-misc-improvements/1/artifact/build-artifacts/00:32:03_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_tca-misc-improvements/1/artifact/build-artifacts/00:32:03_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.htpdate
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_tca-misc-improvements/1/artifact/build-artifacts/00:32:03_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_tca-misc-improvements/1/artifact/build-artifacts/00:32:03_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_tca-misc-improvements/1/artifact/build-artifacts/00:32:03_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_tca-misc-improvements/1/artifact/build-artifacts/00:32:03_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal
After features/support/hooks.rb:100 0.063
Feature: Tails persistence
Tags: @product
36:37.430
Scenario Tails Persistent Storage behave tests
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Steps
Given I have started Tails from DVD and logged in with an administration password and the network is connected 1:37.414
And I update APT using apt 35:0.016
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/misc_helpers.rb:180:in `new'
./features/support/helpers/misc_helpers.rb:180:in `force_new_tor_circuit'
./features/support/helpers/misc_helpers.rb:192:in `block in retry_tor'
./features/support/helpers/misc_helpers.rb:222:in `rescue in block in retry_action'
./features/support/helpers/misc_helpers.rb:209:in `block in retry_action'
./features/support/helpers/misc_helpers.rb:208:in `loop'
./features/support/helpers/misc_helpers.rb:208:in `retry_action'
./features/support/helpers/misc_helpers.rb:196:in `retry_tor'
./features/step_definitions/apt.rb:59:in `/^I update APT using apt$/'
features/persistence.feature:8:in `And I update APT using apt'
And I install "python3-behave" using apt 0.000
Then the Tails Persistent Storage behave tests pass 0.000
After features/support/hooks.rb:330 10.797 
SCENARIO FAILED: 'Tails Persistent Storage behave tests' (at time 03:51:55)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_tca-misc-improvements/1/artifact/build-artifacts/03:51:55_Tails_Persistent_Storage_behave_tests.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_tca-misc-improvements/1/artifact/build-artifacts/03:51:55_Tails_Persistent_Storage_behave_tests.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_tca-misc-improvements/1/artifact/build-artifacts/03:51:55_Tails_Persistent_Storage_behave_tests.journal
After features/support/hooks.rb:100 0.000
Feature: Tails persistence
Tags: @product @doc
21:27.328
Scenario Filesystem and I/O errors
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 with a persistent partition and stopped at Tails Greeter's login screen 9.896
And I corrupt the Persistent Storage filesystem on USB drive "__internal" in a way which can't be automatically repaired 6.224
And Tails detects disk read failures on the boot device 1.616
When I try to enable persistence 0.447
Then the Welcome Screen tells me that my hardware is probably failing 19.047
When I log in to a new session 49.910
And all notifications have disappeared 20:0.186
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:719:in `new'
./features/step_definitions/common_steps.rb:719:in `/^all notifications have disappeared$/'
features/persistence.feature:212:in `And all notifications have disappeared'
Then the Tor Browser starts 0.000
And "Tails - Recovering data from the Persistent Storage when it has file system errors" has loaded in the Tor Browser 0.000
After features/support/hooks.rb:330 11.113 
SCENARIO FAILED: 'Filesystem and I/O errors' (at time 04:50:13)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_tca-misc-improvements/1/artifact/build-artifacts/04:50:13_Filesystem_and_I_O_errors.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_tca-misc-improvements/1/artifact/build-artifacts/04:50:13_Filesystem_and_I_O_errors.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_tca-misc-improvements/1/artifact/build-artifacts/04:50:13_Filesystem_and_I_O_errors.journal
After features/support/hooks.rb:100 0.000