Project

General

Profile

Actions

action #42803

closed

[functional][u][aarch64] Test fails in bootloader_uefi

Added by szarate over 5 years ago. Updated about 5 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Bugs in existing tests
Target version:
SUSE QA - Milestone 22
Start date:
2018-10-23
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

openQA test in scenario sle-12-SP4-Server-DVD-aarch64-RAID1@aarch64 fails in
bootloader_uefi

Problem seems to be again, bootloader taking too long

Reproducible

Fails since (at least) Build 0432 (current job)

Expected result

Last good: 0431 (or more recent)

Further details

Always latest result in this scenario: latest

Actions #1

Updated by szarate over 5 years ago

  • Subject changed from [aarch64]test fails in bootloader_uefi to [aarch64] Test fails in bootloader_uefi

I think it was discused at some point to set it to 60... however, 45for the time being... https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/6023

Actions #2

Updated by szarate over 5 years ago

  • Subject changed from [aarch64] Test fails in bootloader_uefi to [functional][u][aarch64] Test fails in bootloader_uefi
Actions #3

Updated by szarate over 5 years ago

  • Status changed from New to Feedback
  • Assignee set to szarate

PR merged, will leave in feedback for the time being.

Actions #4

Updated by okurz over 5 years ago

  • Target version set to Milestone 21
Actions #5

Updated by szarate over 5 years ago

  • Status changed from Feedback to Resolved

Haven't heard anything about this for a while

Actions #6

Updated by szarate about 5 years ago

  • Status changed from Resolved to Workable
  • Target version changed from Milestone 21 to Milestone 22

Failed again: https://openqa.suse.de/tests/2418807#step/bootloader_uefi/6 so reopening, suggestion is: check for either tianocore screen or actual bootloader, try to boot once again if the tianocore bootloader screen detected instead.

Actions #7

Updated by okurz about 5 years ago

  • Assignee deleted (szarate)
  • Priority changed from Normal to Immediate

It might be that this is intermittent and goes away by itself but we should treat it immediately for now as it looked to me as many jobs of SLE15SP1 are affected.

Actions #8

Updated by mgriessmeier about 5 years ago

  • Status changed from Workable to Feedback
  • Assignee set to mgriessmeier
  • Priority changed from Immediate to Normal

no current fails in milestone build

Actions #9

Updated by mgriessmeier about 5 years ago

  • Status changed from Feedback to Resolved

not seen anymore

Actions

Also available in: Atom PDF