Project

General

Profile

Bug #13459

Bug #10288: Fix newly identified issues to make our test suite more robust and faster

Scenario "Booting Tails from a USB drive in UEFI mode" is fragile

Added by bertagaz over 2 years ago. Updated 9 months ago.

Status:
Confirmed
Priority:
Normal
Assignee:
-
Category:
Test suite
Target version:
-
Start date:
07/12/2017
Due date:
% Done:

0%

Feature Branch:
test/13459-UEFI-scenario-is-fragile
Type of work:
Code
Blueprint:
Starter:
Affected tool:

Description

Happened 30 times in June, 58 for what 2017 logs we had on July 10th.

Test suite can not find the kernel boot command line, and loop over reseting the VM as expected, but eventually fails. Could it be that we need to wait a bit more longer for the UEFI firmware to boot?

Attaching typical mkv and debug.log.

00_51_40_Booting_Tails_from_a_USB_drive_in_UEFI_mode.mkv (229 KB) bertagaz, 07/12/2017 11:43 AM

stable_814.log View (1.17 MB) bertagaz, 07/12/2017 11:44 AM

debug-37.log View (1.16 MB) intrigeri, 09/09/2017 04:23 PM

00_48_06_Booting_Tails_from_a_USB_drive_in_UEFI_mode.mkv (244 KB) intrigeri, 09/09/2017 04:23 PM


Related issues

Related to Tails - Feature #12289: Deal with June 2017 false positive scenarios Resolved 06/05/2017 07/05/2017
Related to Tails - Bug #16820: UEFI test is broken for Tails based on buster Resolved

Associated revisions

Revision 90b73d38 (diff)
Added by bertagaz over 2 years ago

Test suite: mark UEFI scenario as fragile (refs: #13459).

Revision 92345f74 (diff)
Added by bertagaz over 2 years ago

Revert "Test suite: mark UEFI scenario as fragile (refs: #13459)."

This reverts commit 90b73d389137425e965b0bb8d9a3235b3ceab4a2.

History

#1 Updated by bertagaz over 2 years ago

  • Feature Branch set to bugfix/13459-UEFI-scenario-is-fragile

#2 Updated by bertagaz over 2 years ago

  • Related to Feature #12289: Deal with June 2017 false positive scenarios added

#3 Updated by bertagaz over 2 years ago

  • Status changed from Confirmed to In Progress

#4 Updated by intrigeri over 2 years ago

  • Assignee deleted (anonym)
  • Target version deleted (Tails_3.2)

(Please clarify if there's any reason why this should be handled that urgently compared to sibling tickets.)

#5 Updated by intrigeri over 2 years ago

So we're doing "We missed the boot menu before we could deal with it, resetting..." a number of time before the boot menu could actually appear. Looks as if lizard was particularly loaded at that time. And on the last try the boot menu does eventually appear but we stop waiting (the 3 minutes boot_timeout has expired) before the tab spammer could open the boot command line. In this specific case, presumably a slightly larger boot_timeout would have been enough, but I don't think that's the root cause of the problem: screen.wait('UEFIFirmwareSetup.png', 30) wrongly matches something on the screen: I don't see the firmware setup on the video, but there are a few [log] TYPE "#ENTER." followed by a reset in the logs. Perhaps some OVMF upgrade changed its behaviour and now our special handling code is somewhat obsolete and behaving weirdly? It seems that this code is making things less robust in some cases, by repeatedly resetting a system that otherwise would perhaps boot just fine.

It's tempting to drop the UEFI firmware setup handling code, or to update that picture, and see what happens.

I've seen 2 runs of the — erroneously named BTW — topic branch (Aug 30, Aug 31) that exposed exactly the same behavior.

#6 Updated by intrigeri over 2 years ago

  • Feature Branch changed from bugfix/13459-UEFI-scenario-is-fragile to test/13459-UEFI-scenario-is-fragile

(Fixed branch name, deleted the old one.)

#7 Updated by intrigeri 9 months ago

  • Status changed from In Progress to Confirmed

#8 Updated by intrigeri 6 months ago

  • Related to Bug #16820: UEFI test is broken for Tails based on buster added

Also available in: Atom PDF