Project Number Date
test_Tails_ISO_20268-more-early-patch-functionality 49 20 Apr 2024, 06:31

Failures Overview

The following summary displays scenarios that failed.

Tags: @product
5:24.405
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.399
And I wait until Tor is ready 3.916
When I disconnect the network through GNOME 2.841
And I connect the network through GNOME 2.802
Then the Tor Connection Assistant autostarts 2.402
And the Tor Connection Assistant connects to Tor 4.669
And I wait until Tor is ready 5:0.373
Time syncing failed (HtpdateError)
./features/step_definitions/common_steps.rb:703:in `rescue in block in <top (required)>'
./features/step_definitions/common_steps.rb:701:in `/^the time has synced$/'
./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:305 4.409

SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:30:10)

Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/49/artifact/build-artifacts/00:30:10_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected_chutney-data

Htpdate logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/49/artifact/build-artifacts/00:30:10_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.htpdate

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/49/artifact/build-artifacts/00:30:10_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png

Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/49/artifact/build-artifacts/00:30:10_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.tor

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/49/artifact/build-artifacts/00:30:10_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/49/artifact/build-artifacts/00:30:10_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/49/artifact/build-artifacts/00:30:10_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal

After features/support/hooks.rb:89 0.065
Tags: @product
34.197
Scenario The included APT repository keys are up-to-date
Before features/support/hooks.rb:259 0.005
Steps
Given I have started Tails from DVD without network and logged in 21.194
Then the keys trusted by APT are valid for the next 3 months 13.003
The
The following APT key(s) will not be valid in 3 months: A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89, 2265EB4CB2BF88D900AE8D1B74A941BA219EC810.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/checks.rb:29:in `assert_all_keys_are_valid_for_n_months'
./features/step_definitions/checks.rb:8:in `/^the keys trusted by APT are valid for the next (\d+) months$/'
features/keys.feature:11:in `Then the keys trusted by APT are valid for the next 3 months'
After features/support/hooks.rb:305 4.461

SCENARIO FAILED: 'The included APT repository keys are up-to-date' (at time 02:16:15)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/49/artifact/build-artifacts/02:16:15_The_included_APT_repository_keys_are_up-to-date.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/49/artifact/build-artifacts/02:16:15_The_included_APT_repository_keys_are_up-to-date.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/49/artifact/build-artifacts/02:16:15_The_included_APT_repository_keys_are_up-to-date.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/49/artifact/build-artifacts/02:16:15_The_included_APT_repository_keys_are_up-to-date.journal

After features/support/hooks.rb:89 0.000
Tags: @product
1:55.379
Scenario MAC address spoofing fails and the module is not removed
Before features/support/hooks.rb:259 0.008
Steps
Given I have started Tails from DVD without network and stopped at Tails Greeter's login screen 8.080
And I capture all network traffic 0.008
And the network is plugged 0.046
And macchanger will fail by not spoofing and always returns true 0.192
And no network interface modules can be unloaded 0.468
When I log in to a new session 1:46.081
Then 1 network interface is enabled 0.260
But the MAC spoofing panic mode disabled networking 0.239
NetworkManager was not disabled.
<nil> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/mac_spoofing.rb:94:in `/^the MAC spoofing panic mode disabled networking$/'
features/mac_spoofing.feature:63:in `But the MAC spoofing panic mode disabled networking'
And no network device leaked the real MAC address 0.000
And I see the "All networking disabled" notification after at most 60 seconds 0.000
After features/support/hooks.rb:305 4.246

SCENARIO FAILED: 'MAC address spoofing fails and the module is not removed' (at time 02:51:07)

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/49/artifact/build-artifacts/02:51:07_MAC_address_spoofing_fails_and_the_module_is_not_removed.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/49/artifact/build-artifacts/02:51:07_MAC_address_spoofing_fails_and_the_module_is_not_removed.mkv

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/49/artifact/build-artifacts/02:51:07_MAC_address_spoofing_fails_and_the_module_is_not_removed.boot-log

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20268-more-early-patch-functionality/49/artifact/build-artifacts/02:51:07_MAC_address_spoofing_fails_and_the_module_is_not_removed.journal

After features/support/hooks.rb:89 0.060