Project Number Date
test_Tails_ISO_20530-tca-controls-tor-flag-file 61 21 Dec 2024, 21:25

Failures Overview

The following summary displays scenarios that failed.

Feature: Using Tor bridges and pluggable transports
Tags: @product
4:54.331
Scenario The same Tor configuration is applied when the network is reconnected
Steps
Given I configure a direct connection in the Tor Connection Assistant 8.970
And I wait until Tor is ready 3.484
When I disconnect the network through GNOME 3.039
And I connect the network through GNOME 2.675
Then the Tor Connection Assistant autostarts 2.378
And the Tor Connection Assistant connects to Tor 3.685
And I wait until Tor is ready 4:30.098
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:261:in `rescue in wait_until_tor_is_working'
./features/support/helpers/misc_helpers.rb:254:in `wait_until_tor_is_working'
./features/step_definitions/common_steps.rb:692:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:654: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:326 5.358 
SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:30:34)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/61/artifact/build-artifacts/00:30:34_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/61/artifact/build-artifacts/00:30:34_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/61/artifact/build-artifacts/00:30:34_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/61/artifact/build-artifacts/00:30:34_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/61/artifact/build-artifacts/00:30:34_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/61/artifact/build-artifacts/00:30:34_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal
After features/support/hooks.rb:100 0.050
Feature: System memory erasure on shutdown
Tags: @product @slow @not_release_blocker
27:2.428
Scenario Erasure of read and write disk caches of persistent data on shutdown
Before features/support/hooks.rb:269 0.003
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 27:2.428
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:712:in `new'
./features/step_definitions/common_steps.rb:712:in `/^all notifications have disappeared$/'
./features/step_definitions/snapshots.rb:153:in `block in reach_checkpoint'
./features/step_definitions/snapshots.rb:150:in `each'
./features/step_definitions/snapshots.rb:150:in `reach_checkpoint'
./features/step_definitions/snapshots.rb:173:in `/^I\ have\ started\ Tails\ without\ network\ from\ a\ USB\ drive\ with\ a\ persistent\ partition\ enabled\ and\ logged\ in$/'
features/erase_memory.feature:75:in `Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in'
And I prepare Tails for memory erasure tests 0.000
When I fill a 128 MiB file with a known pattern on the persistent filesystem 0.000
When I trigger shutdown 0.000
Then I find very few patterns in the guest's memory after 20 seconds 0.000
After features/support/hooks.rb:326 11.067 
SCENARIO FAILED: 'Erasure of read and write disk caches of persistent data on shutdown' (at time 01:03:48)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/61/artifact/build-artifacts/01:03:48_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/61/artifact/build-artifacts/01:03:48_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20530-tca-controls-tor-flag-file/61/artifact/build-artifacts/01:03:48_Erasure_of_read_and_write_disk_caches_of_persistent_data_on_shutdown.journal
After features/support/hooks.rb:100 0.016