action #105046
closedAdd workaround for bsc#1191112 in test suites affected
Description
Motivation¶
Add workaround to continue testing as this bug is still in progress for a long time.
Example:
When clicking with the mouse at this point https://openqa.suse.de/tests/7976962#step/yast2_security/16
we should see another screen.
Scope¶
yast2_gui and if possible some other test suites affected (search for it in latest build)
Acceptance criteria¶
AC1: Add workaround to see the next screen in the affected places
AC2: Keep providing info in bsc#1191112
Further info¶
The bug appears always in the same place, so might worth to try.
For yast2_snapper was applied recently in this PR https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/14041 which is the next test executed in the same test suite, for that we had created [another bug](https://bugzilla.suse.com/show_bug.cgi?id=1190217 that at the end turned to be this known bug with the refreshment of the screen.
Suggestion¶
Try send_key 'alt-F10' maximize/minimize.
If we find a realiable workaround, apply it everywhere even in the places where we put other hacks to do it.
Updated by JERiveraMoya almost 3 years ago
- Subject changed from Add workaround for bsc#1191112 in yast2 security to Add workaround for bsc#1191112 in test suites affected
- Description updated (diff)
Updated by JERiveraMoya almost 3 years ago
- Tags deleted (
qe-yast-refinement) - Description updated (diff)
- Status changed from New to Workable
Updated by JERiveraMoya over 2 years ago
could we also apply the workaround here? https://openqa.suse.de/tests/8208233#step/iscsi_server/55
Updated by geor over 2 years ago
JERiveraMoya wrote:
could we also apply the workaround here? https://openqa.suse.de/tests/8208233#step/iscsi_server/55
Yes, good catch!
Updated by JERiveraMoya over 2 years ago
Another one to apply the workaround, the more subtle I saw until now, you can see in the video that for a moment the title change but nothing else in the screen (in most of the case was the contrary): https://openqa.suse.de/tests/8216576#step/nis_server/39
Feel free to file additional ticket about that if you think there are too many places to make the fix.
Updated by geor over 2 years ago
Updated by JERiveraMoya over 2 years ago
- Status changed from In Progress to Feedback
Updated by openqa_review over 2 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: sles+sdk+proxy_SCC_via_YaST
https://openqa.suse.de/tests/8376981
To prevent further reminder comments one of the following options should be followed:
- The test scenario is fixed by applying the bug fix to the tested product or the test is adjusted
- The openQA job group is moved to "Released" or "EOL" (End-of-Life)
- The bugref in the openQA scenario is removed or replaced, e.g.
label:wontfix:boo1234
Expect the next reminder at the earliest in 28 days if nothing changes in this ticket.