Project

General

Profile

Actions
Copy link

action #88199

closed

[Sporadic] Test fails with "unknown pop-up message" but there is no pop-up

Added by JRivrain about 3 years ago. Updated about 3 years ago.

Status:
Rejected
Priority:
Low
Assignee:
JERiveraMoya
Target version:
SUSE QA - SLE 15 SP3
Start date:
2021-01-25
Due date:
% Done:

0%

Estimated time:

Description

Observation

The problem is that we match known warning, but on the next iteration of the loop it is still shown and as we have already processed in the test code, we fail as it appears to be another warning.
Solution would be to either ensure that warning was closed before next iteration, or be more tolerant with waiting.
NOTE: issue is very rare, so does not require hammering ;)

It looks like the pop-up here was closed before being asserted again.

[2021-01-25T16:48:26.895 CET] [debug] >>> testapi::_handle_found_needle: found installation-autoyast-boot-20201009, similarity 1.00 @ 325/305
[2021-01-25T16:48:26.897 CET] [debug] tests/autoyast/installation.pm:215 called testapi::check_screen
[2021-01-25T16:48:26.897 CET] [debug] <<< testapi::check_screen(mustmatch="warning-partition-reduced", timeout=0)
[2021-01-25T16:48:27.064 CET] [debug] no match: -0.1s, best candidate: autoyast-warning-partition-reduced-20170609 (0.00)
[2021-01-25T16:48:27.269 CET] [debug] >>> testapi::_check_backend_response: match=warning-partition-reduced timed out after 0 (check_screen)
[2021-01-25T16:48:27.300 CET] [debug] tests/autoyast/installation.pm:225 called installation::handle_warnings -> tests/autoyast/installation.pm:92 called testapi::check_screen
[2021-01-25T16:48:27.300 CET] [debug] <<< testapi::check_screen(mustmatch="autoyast-known-warning", timeout=0)
[2021-01-25T16:48:30.229 CET] [debug] WARNING: check_asserted_screen took 2.33 seconds for 14 candidate needles - make your needles more specific
[2021-01-25T16:48:30.229 CET] [debug] no match: -0.7s, best candidate: autoyast-warning-shrinking-20191218 (0.18)
[2021-01-25T16:48:30.434 CET] [debug] >>> testapi::_check_backend_response: match=autoyast-known-warning timed out after 0 (check_screen)
[2021-01-25T16:48:30.616 CET] [info] ::: basetest::runtest: # Test died: Unknown popup message at /var/lib/openqa/cache/openqa.suse.de/tests/sle/tests/autoyast/installation.pm line 92.

openQA test in scenario sle-15-SP3-Online-x86_64-autoyast_lvm@64bit fails in
installation

Test suite description

AutoYaST installation using LVM for partitioning, having GPT with /, /opt and
swap Logical Volumes in a single Volume Group. Following is validated in the SUT:

  • LVM configuration.
  • Firewall configuration.
  • Subvolumes configuration.
  • Passwords are set for the users in the profile.

Reproducible

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

Expected result

Last good: 130.3 (or more recent)

Further details

Always latest result in this scenario: latest

Actions
Copy link
 #1

Updated by JRivrain about 3 years ago

  • Project changed from openQA Tests to qe-yam
  • Category deleted (Bugs in existing tests)
Actions
Copy link
 #2

Updated by JRivrain about 3 years ago

  • Subject changed from Test fails with "unknown pop-up message" but there is no pop-up to [Sporadic] Test fails with "unknown pop-up message" but there is no pop-up
Actions
Copy link
 #3

Updated by riafarov about 3 years ago

  • Description updated (diff)
  • Status changed from New to Workable
  • Priority changed from Normal to Low
  • Target version set to SLE 15 SP3
Actions
Copy link
 #4

Updated by JERiveraMoya about 3 years ago

  • Status changed from Workable to In Progress
  • Assignee set to JERiveraMoya
Actions
Copy link
 #6

Updated by okurz about 3 years ago

This is an autogenerated message for openQA integration by the openqa_review script:

This bug is still referenced in a failing openQA test: autoyast_lvm
https://openqa.suse.de/tests/5524983

To prevent further reminder comments one of the following options should be followed:

  1. The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
  2. The openQA job group is moved to "Released"
  3. The label in the openQA scenario is removed
Actions
Copy link

Also available in: Atom PDF