Project Number Date
test_Tails_ISO_arti-1.4.3 1 09 May 2025, 00:49

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Getting a DHCP lease without leaking too much information 6 2 8 0 0 16 0 2 2 9:44.074 Failed
Tags: @product
Feature Getting a DHCP lease without leaking too much information
As a Tails user when I connect to a network with a DHCP server I should be able to connect to the Internet and the hostname should not have been leaked on the network.
4:52.187
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.003
Steps
Given I have started Tails from DVD without network and logged in 8.335
And I capture all network traffic 0.006
And the network is plugged 0.077
And Tor is ready 4:43.769
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272: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:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
./features/step_definitions/common_steps.rb:667:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:618:in `/^Tor is ready$/'
features/dhcp.feature:12:in `And Tor is ready'
And all notifications have disappeared 0.000
And available upgrades have been checked 0.000
Tags: @product
0.000
Scenario Getting a DHCP lease with the default NetworkManager connection
Steps
Then the hostname should not have been leaked on the network 0.000
After features/support/hooks.rb:330 5.813 
SCENARIO FAILED: 'Getting a DHCP lease with the default NetworkManager connection' (at time 03:08:47)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/1/artifact/build-artifacts/03:08:47_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/1/artifact/build-artifacts/03:08:47_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/1/artifact/build-artifacts/03:08:47_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/1/artifact/build-artifacts/03:08:47_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/1/artifact/build-artifacts/03:08:47_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/1/artifact/build-artifacts/03:08:47_Getting_a_DHCP_lease_with_the_default_NetworkManager_connection.journal
After features/support/hooks.rb:100 0.067
4:51.886
Background
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.004
Steps
Given I have started Tails from DVD without network and logged in 9.785
And I capture all network traffic 0.005
And the network is plugged 0.646
And Tor is ready 4:41.448
Tor 
Tor failed to bootstrap (TorBootstrapFailure)
./features/support/helpers/misc_helpers.rb:272: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:710:in `/^Tor has built a circuit$/'
./features/step_definitions/common_steps.rb:672:in `/^I wait until Tor is ready$/'
./features/step_definitions/common_steps.rb:667:in `/^I successfully configure Tor$/'
./features/step_definitions/common_steps.rb:618:in `/^Tor is ready$/'
features/dhcp.feature:12:in `And Tor is ready'
And all notifications have disappeared 0.000
And available upgrades have been checked 0.000
Tags: @product
0.000
Scenario Getting a DHCP lease with a manually configured NetworkManager connection
Steps
When I add a wired DHCP NetworkManager connection called "manually-added-con" 0.000
And I switch to the "manually-added-con" NetworkManager connection 0.000
Then the hostname should not have been leaked on the network 0.000
After features/support/hooks.rb:330 5.542 
SCENARIO FAILED: 'Getting a DHCP lease with a manually configured NetworkManager connection' (at time 03:13:45)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/1/artifact/build-artifacts/03:13:45_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/1/artifact/build-artifacts/03:13:45_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/1/artifact/build-artifacts/03:13:45_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/1/artifact/build-artifacts/03:13:45_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/1/artifact/build-artifacts/03:13:45_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_arti-1.4.3/1/artifact/build-artifacts/03:13:45_Getting_a_DHCP_lease_with_a_manually_configured_NetworkManager_connection.journal
After features/support/hooks.rb:100 0.058