Project Number Date
test_Tails_ISO_20263-remote-shell-debug-logging 5 06 Mar 2025, 15:27

Failures Overview

The following summary displays scenarios that failed.

Feature: Using Tor bridges and pluggable transports
Tags: @product
5:27.683
Scenario The same Tor configuration is applied when the network is reconnected
Steps
Given I configure a direct connection in the Tor Connection Assistant 11.030
And I wait until Tor is ready 1.481
When I disconnect the network through GNOME 3.153
And I connect the network through GNOME 3.175
Then the Tor Connection Assistant autostarts 1.761
And the Tor Connection Assistant connects to Tor 6.805
And I wait until Tor is ready 5:0.276
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.166 
SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:30:41)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20263-remote-shell-debug-logging/5/artifact/build-artifacts/00:30:41_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20263-remote-shell-debug-logging/5/artifact/build-artifacts/00:30:41_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_20263-remote-shell-debug-logging/5/artifact/build-artifacts/00:30:41_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.htpdate
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20263-remote-shell-debug-logging/5/artifact/build-artifacts/00:30:41_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20263-remote-shell-debug-logging/5/artifact/build-artifacts/00:30:41_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20263-remote-shell-debug-logging/5/artifact/build-artifacts/00:30:41_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20263-remote-shell-debug-logging/5/artifact/build-artifacts/00:30:41_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal
After features/support/hooks.rb:100 0.054
Feature: Tails persistence
Tags: @product
22:53.773
Scenario Changing the Persistent Storage passphrase
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 enabled and logged in 10.235
# Note that if anything fails after the passphrase was changed and
# before it's changed back below, subsequent scenarios might fail
# because the Persistent Storage doesn't have the expected passphrase.
When I change the passphrase of the Persistent Storage 31.692
And I shutdown Tails and wait for the computer to power off 14.793
Then I start Tails from USB drive "__internal" with network unplugged and I login with the changed persistence passphrase 21:57.051
execution 
execution expired (RemoteShell::Timeout)
./features/support/helpers/remote_shell.rb:62:in `read'
./features/support/helpers/remote_shell.rb:62:in `block (3 levels) in communicate'
./features/support/helpers/remote_shell.rb:61:in `block (2 levels) in communicate'
./features/support/helpers/remote_shell.rb:44:in `loop'
./features/support/helpers/remote_shell.rb:44:in `block in communicate'
./features/support/helpers/remote_shell.rb:37:in `communicate'
./features/support/helpers/remote_shell.rb:182:in `execute'
./features/support/helpers/remote_shell.rb:193:in `initialize'
./features/support/helpers/dogtail.rb:81:in `new'
./features/support/helpers/dogtail.rb:81:in `block in run'
./features/support/helpers/dogtail.rb:80:in `each'
./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:123:in `Then I start Tails from USB drive "__internal" with network unplugged and I login with the changed persistence passphrase'
And I change the passphrase of the Persistent Storage back to the original 0.000
After features/support/hooks.rb:330 10.939 
SCENARIO FAILED: 'Changing the Persistent Storage passphrase' (at time 03:59:50)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20263-remote-shell-debug-logging/5/artifact/build-artifacts/03:59:50_Changing_the_Persistent_Storage_passphrase.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20263-remote-shell-debug-logging/5/artifact/build-artifacts/03:59:50_Changing_the_Persistent_Storage_passphrase.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20263-remote-shell-debug-logging/5/artifact/build-artifacts/03:59:50_Changing_the_Persistent_Storage_passphrase.journal
After features/support/hooks.rb:100 0.010