Project

General

Profile

Actions

action #114550

open

[qe-core] Ignored warnings about too many needles and detected stalls, in particular when checking grub2

Added by okurz almost 2 years ago. Updated 3 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Enhancement to existing tests
Target version:
-
Start date:
2022-07-22
Due date:
% Done:

0%

Estimated time:
Difficulty:

Description

Observation

I again found the problem when working on #114523, e.g. see https://openqa.suse.de/tests/9196630#, the test passes but has warnings about "too many needles" and often also stalls detected:

[2022-07-22T10:19:58.090574+02:00] [debug] <<< testapi::assert_screen(mustmatch=[
    "bootloader-shim-import-prompt",
    "bootloader-grub2"
  ], timeout=90)
[2022-07-22T10:20:00.158791+02:00] [warn] !!! backend::baseclass::check_asserted_screen: check_asserted_screen took 1.10 seconds for 18 candidate needles - make your needles more specific
[2022-07-22T10:20:00.159265+02:00] [debug] no match: 89.0s, best candidate: bootloader_uefi-20170718 (0.00)
[2022-07-22T10:20:00.169228+02:00] [debug] no change: 87.9s
[2022-07-22T10:20:00.827311+02:00] [warn] !!! backend::baseclass::check_asserted_screen: check_asserted_screen took 0.66 seconds for 18 candidate needles - make your needles more specific
[2022-07-22T10:20:00.827754+02:00] [debug] no match: 87.9s, best candidate: bootloader_uefi-20170718 (0.00)
[2022-07-22T10:20:01.161710+02:00] [debug] no change: 86.9s
[2022-07-22T10:20:01.813958+02:00] [warn] !!! backend::baseclass::check_asserted_screen: check_asserted_screen took 0.65 seconds for 18 candidate needles - make your needles more specific
[2022-07-22T10:20:01.814389+02:00] [debug] no match: 86.9s, best candidate: bootloader_uefi-20170718 (0.00)
[2022-07-22T10:20:10.820216+02:00] [warn] !!! backend::baseclass::check_asserted_screen: check_asserted_screen took 8.66 seconds for 18 candidate needles - make your needles more specific
[2022-07-22T10:20:10.820681+02:00] [debug] no match: 85.9s, best candidate: bootloader_uefi-20170718 (0.00)
[2022-07-22T10:20:10.831137+02:00] [debug] no change: 77.2s
[2022-07-22T10:20:11.490641+02:00] [warn] !!! backend::baseclass::check_asserted_screen: check_asserted_screen took 0.66 seconds for 18 candidate needles - make your needles more specific
[2022-07-22T10:20:11.491133+02:00] [debug] no match: 77.2s, best candidate: bootloader_uefi-20170718 (0.00)
[2022-07-22T10:20:11.824198+02:00] [debug] no change: 76.2s
[2022-07-22T10:20:12.479708+02:00] [warn] !!! backend::baseclass::check_asserted_screen: check_asserted_screen took 0.65 seconds for 18 candidate needles - make your needles more specific
[2022-07-22T10:20:12.480137+02:00] [debug] no match: 76.2s, best candidate: bootloader_uefi-20170718 (0.00)
[2022-07-22T10:20:21.382495+02:00] [warn] !!! backend::baseclass::check_asserted_screen: check_asserted_screen took 8.56 seconds for 18 candidate needles - make your needles more specific
[2022-07-22T10:20:21.382965+02:00] [debug] no match: 75.2s, best candidate: bootloader_uefi-20170718 (0.00)
[2022-07-22T10:20:22.438398+02:00] [warn] !!! backend::baseclass::check_asserted_screen: check_asserted_screen took 1.03 seconds for 18 candidate needles - make your needles more specific
[2022-07-22T10:20:22.438858+02:00] [debug] no match: 66.6s, best candidate: bootloader_uefi-20170718 (0.00)
[2022-07-22T10:20:31.620043+02:00] [warn] !!! backend::baseclass::check_asserted_screen: check_asserted_screen took 9.14 seconds for 18 candidate needles - make your needles more specific
[2022-07-22T10:20:31.620500+02:00] [debug] no match: 65.6s, best candidate: bootloader_uefi-20170718 (0.00)
[2022-07-22T10:20:32.589253+02:00] [warn] !!! backend::baseclass::check_asserted_screen: check_asserted_screen took 0.94 seconds for 18 candidate needles - make your needles more specific
[2022-07-22T10:20:32.589735+02:00] [debug] no match: 56.4s, best candidate: bootloader_uefi-20170718 (0.00)

Eventually we might need to turn the warning into a fatal error and fail the tests but to allow graceful handling I am creating this ticket so that you have a chance to fix those problems before they fail more tests.

Acceptance criteria

  • AC1: Usual tests do not show any warnigs related to "make your needles more specific"

Related issues 1 (1 open0 closed)

Related to openQA Infrastructure - action #114523: Deal with QEMU and OVMF default resolution being 1280x800, affecting (at least) qxl, but on aarch64 size:MWorkable2022-06-03

Actions
Actions #1

Updated by okurz almost 2 years ago

  • Related to action #114523: Deal with QEMU and OVMF default resolution being 1280x800, affecting (at least) qxl, but on aarch64 size:M added
Actions #2

Updated by slo-gin 3 months ago

This ticket was set to Normal priority but was not updated within the SLO period. Please consider picking up this ticket or just set the ticket to the next lower priority.

Actions

Also available in: Atom PDF