Project Number Date
test_Tails_ISO_devel 3425 13 Jun 2024, 13:14

Failures Overview

The following summary displays scenarios that failed.

Feature: Using Tor bridges and pluggable transports
Tags: @product
5:27.322
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.012
And I wait until Tor is ready 5.506
When I disconnect the network through GNOME 3.172
And I connect the network through GNOME 3.474
Then the Tor Connection Assistant autostarts 2.910
And the Tor Connection Assistant connects to Tor 3.884
And I wait until Tor is ready 5:0.359
Time 
Time syncing failed (HtpdateError)
./features/step_definitions/common_steps.rb:705:in `rescue in block in <top (required)>'
./features/step_definitions/common_steps.rb:703:in `/^the time has synced$/'
./features/step_definitions/common_steps.rb:656: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:315 5.498 
SCENARIO FAILED: 'The same Tor configuration is applied when the network is reconnected' (at time 00:32:52)
Chutney logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3425/artifact/build-artifacts/00:32:52_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected_chutney-data
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3425/artifact/build-artifacts/00:32:52_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_devel/3425/artifact/build-artifacts/00:32:52_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.htpdate
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3425/artifact/build-artifacts/00:32:52_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.png
Tor logs: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3425/artifact/build-artifacts/00:32:52_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.tor
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3425/artifact/build-artifacts/00:32:52_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3425/artifact/build-artifacts/00:32:52_The_same_Tor_configuration_is_applied_when_the_network_is_reconnected.journal
After features/support/hooks.rb:100 0.037
Feature: Installing Tails to a USB drive
Tags: @product @uefi
3:13.946
Scenario Booting Tails from a USB drive in UEFI mode
Before features/support/hooks.rb:269 0.004
Steps
Given I have started Tails without network from a USB drive without a persistent partition and stopped at Tails Greeter's login screen 12.417
And I power off the computer 0.325
And the computer is set to boot in UEFI mode 0.029
When I start Tails from USB drive "__internal" with network unplugged and I login 3:1.173
try_for() 
try_for() timeout expired
Last ignored exception was: FindFailed: can not find any of the patterns ["TailsBootMenuKernelCmdlineUEFI_Bullseye.png", "TailsBootMenuKernelCmdlineUEFI_Bookworm.png"] on the screen
./features/support/helpers/screen.rb:240:in `rescue in wait_any'
./features/support/helpers/screen.rb:224:in `wait_any'
./features/step_definitions/common_steps.rb:417:in `block in enter_boot_menu_cmdline'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
./features/support/helpers/misc_helpers.rb:66:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/common_steps.rb:402:in `enter_boot_menu_cmdline'
./features/step_definitions/common_steps.rb:432:in `the_computer_boots'
./features/step_definitions/common_steps.rb:446:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:287:in `block in <top (required)>' (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/common_steps.rb:402:in `enter_boot_menu_cmdline'
./features/step_definitions/common_steps.rb:432:in `the_computer_boots'
./features/step_definitions/common_steps.rb:446:in `/^the computer (?:re)?boots Tails( with genuine APT sources)?$/'
./features/step_definitions/common_steps.rb:287: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/usb_install.feature:85:in `When I start Tails from USB drive "__internal" with network unplugged and I login'
Then Tails is running from USB drive "__internal" 0.000
And the boot device has safe access rights 0.000
And Tails has started in UEFI mode 0.000
After features/support/hooks.rb:315 10.613 
SCENARIO FAILED: 'Booting Tails from a USB drive in UEFI mode' (at time 01:14:51)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3425/artifact/build-artifacts/01:14:51_Booting_Tails_from_a_USB_drive_in_UEFI_mode.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3425/artifact/build-artifacts/01:14:51_Booting_Tails_from_a_USB_drive_in_UEFI_mode.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3425/artifact/build-artifacts/01:14:51_Booting_Tails_from_a_USB_drive_in_UEFI_mode.journal
After features/support/hooks.rb:100 0.139