Project Number Date
test_Tails_ISO_improved-new-identity-scenario 11 10 May 2025, 13:58

Failures Overview

The following summary displays scenarios that failed.

Tags: @product
5:24.389
Scenario The same Tor configuration is applied when the network is reconnected
Steps
Given I configure a direct connection in the Tor Connection Assistant 6.976
And I wait until Tor is ready 3.949
When I disconnect the network through GNOME 2.993
And I connect the network through GNOME 2.857
Then the Tor Connection Assistant autostarts 2.480
And the Tor Connection Assistant connects to Tor 4.802
And I wait until Tor is ready 5:0.329
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.211

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_improved-new-identity-scenario/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_improved-new-identity-scenario/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_improved-new-identity-scenario/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_improved-new-identity-scenario/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_improved-new-identity-scenario/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_improved-new-identity-scenario/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_improved-new-identity-scenario/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.062
Tags: @product
22:46.580
Scenario Dotfiles persistence
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.015
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 10.819
When I write some dotfile expected to persist 0.111
And I shutdown Tails and wait for the computer to power off 13.250
And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 22:22.399
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:139:in `And I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
Then the expected persistent dotfile is present in the filesystem 0.000
After features/support/hooks.rb:330 10.918

SCENARIO FAILED: 'Dotfiles persistence' (at time 04:09:18)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_improved-new-identity-scenario/11/artifact/build-artifacts/04:09:18_Dotfiles_persistence.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improved-new-identity-scenario/11/artifact/build-artifacts/04:09:18_Dotfiles_persistence.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improved-new-identity-scenario/11/artifact/build-artifacts/04:09:18_Dotfiles_persistence.journal

After features/support/hooks.rb:100 0.010
Tags: @product
3:39.926
Scenario The Tor Browser's circuit view feature works as expected
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.006
Steps
Given I have started Tails from DVD and logged in and the network is connected 13.856
When I start the Tor Browser 25.968
And the Tor Browser loads the startup page 3:0.101
try_for() timeout expired (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/browser.rb:204:in `page_has_loaded_in_the_tor_browser'
./features/step_definitions/browser.rb:498:in `/^the Tor Browser loads the (startup page|Tails homepage|Tails GitLab)$/'
features/torified_browsing.feature:94:in `And the Tor Browser loads the startup page'
Then Tor Browser's circuit view is working 0.000
After features/support/hooks.rb:330 5.890

SCENARIO FAILED: 'The Tor Browser's circuit view feature works as expected' (at time 05:01:34)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_improved-new-identity-scenario/11/artifact/build-artifacts/05:01:34_The_Tor_Browser_s_circuit_view_feature_works_as_expected.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_improved-new-identity-scenario/11/artifact/build-artifacts/05:01:34_The_Tor_Browser_s_circuit_view_feature_works_as_expected.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_improved-new-identity-scenario/11/artifact/build-artifacts/05:01:34_The_Tor_Browser_s_circuit_view_feature_works_as_expected.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_improved-new-identity-scenario/11/artifact/build-artifacts/05:01:34_The_Tor_Browser_s_circuit_view_feature_works_as_expected.journal

After features/support/hooks.rb:100 0.000