Project Number Date
test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix 11 30 Oct 2024, 19:06

Failures Overview

The following summary displays scenarios that failed.

Feature: Installing Tails to a USB drive
Tags: @product @uefi
3:39.978
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 38.292
And I power off the computer 0.348
And the computer is set to boot in UEFI mode 0.037
When I start Tails from USB drive "__internal" with network unplugged and I login 3:1.300
try_for() 
try_for() timeout expired
Last ignored exception was: FindFailed: can not find any of the patterns ["TailsBootMenuGRUB_Bullseye.png", "TailsBootMenuGRUB_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:407: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:404:in `enter_boot_menu_cmdline'
./features/step_definitions/common_steps.rb:434:in `the_computer_boots'
./features/step_definitions/common_steps.rb:448:in `block in <top (required)>'
./features/step_definitions/common_steps.rb:284: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:404:in `enter_boot_menu_cmdline'
./features/step_definitions/common_steps.rb:434:in `the_computer_boots'
./features/step_definitions/common_steps.rb:448:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:284: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:326 10.643 
SCENARIO FAILED: 'Booting Tails from a USB drive in UEFI mode' (at time 01:01:50)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix/11/artifact/build-artifacts/01:01:50_Booting_Tails_from_a_USB_drive_in_UEFI_mode.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix/11/artifact/build-artifacts/01:01:50_Booting_Tails_from_a_USB_drive_in_UEFI_mode.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix/11/artifact/build-artifacts/01:01:50_Booting_Tails_from_a_USB_drive_in_UEFI_mode.journal
After features/support/hooks.rb:100 0.087
Feature: Tails persistence
Tags: @product
2:26.558
Scenario LUKS backup header is restored if something goes wrong during upgrade
Before features/support/hooks.rb:269 0.007
Steps
Given I have started Tails without network from a USB drive with a LUKS 1 persistent partition and stopped at Tails Greeter's login screen 25.789
And I enable persistence but something goes wrong during the LUKS header upgrade 2:0.768
try_for() 
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/usb.rb:683:in `/^persistence is successfully enabled$/'
./features/step_definitions/usb.rb:702:in `/^I enable persistence( with the changed passphrase)?$/'
./features/step_definitions/usb.rb:712:in `/^I enable persistence but something goes wrong during the LUKS header upgrade$/'
features/persistence.feature:162:in `And I enable persistence but something goes wrong during the LUKS header upgrade'
Then the Tails persistence partition on USB drive "__internal" still has LUKS version 1 0.000
After features/support/hooks.rb:326 5.508 
SCENARIO FAILED: 'LUKS backup header is restored if something goes wrong during upgrade' (at time 03:52:20)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix/11/artifact/build-artifacts/03:52:20_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix/11/artifact/build-artifacts/03:52:20_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix/11/artifact/build-artifacts/03:52:20_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_20634-greeter-tps-upgrade-failure-fix/11/artifact/build-artifacts/03:52:20_LUKS_backup_header_is_restored_if_something_goes_wrong_during_upgrade.journal
After features/support/hooks.rb:100 0.000