Project

General

Profile

action #117949

coordination #121876: [epic] Handle openQA review failures in Yam squad

Apply workaround to force screen refresh on YaST Qt window

Added by geor 4 months ago. Updated about 1 month ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
Start date:
2022-10-11
Due date:
% Done:

0%

Estimated time:

Description

Motivation

Occasionally, the screen on a YaST Qt window does not refresh properly (bsc#1204176). This leads to failures like this one where content from the previous screen is still visible in the new screen, and this one where the content does not fully load.
A workaround is to hit shift-F3 twice to bring up the style sheet selection and close it again. This forces a refresh on the YaST screen, as seen here.
We should apply this workaround to all affected areas.

Scope

The workaround should be applied for 15-SP5, all archs.
Concerning which areas of the code would be affected, check the Suggestion section.
Workaround should be applied where is not working now, not everywhere.

Acceptance criteria

AC1: Add a workaround (hitting shift-f3 to open and close the style menu) to force a refresh on the YaST Qt window.
AC2: Make sure to record a soft failure, above the workaround, mentioning the new bug bsc#1204176 as the reason for the workaround.

Suggestion

We used to apply a similar workaround where we would send alt-F10 multiple times (actually, an even number of times), which would maximize and unmaximize the window, forcing a screen refresh.
The workaround was removed with this PR when a fix was added to the new 15-SP5 builds.
However this fix seems to not fully remove the refresh issue.
The suggestion here is to check this PR to view in which areas of the code to introduce the shift-F3 workaround.
So for instance we could re-introduce at the same areas a send_key_until_needlematch but this time with shift-F3.

History

#1 Updated by geor 4 months ago

  • Description updated (diff)

#2 Updated by JERiveraMoya 4 months ago

  • Tags set to qe-yast-refinement

#3 Updated by JERiveraMoya 4 months ago

  • Tags deleted (qe-yast-refinement)
  • Description updated (diff)
  • Status changed from New to Workable

#4 Updated by rainerkoenig 4 months ago

  • Status changed from Workable to In Progress
  • Assignee set to rainerkoenig

#5 Updated by rainerkoenig 3 months ago

Problems on Build 29.1

Pressing Shift-F3 brings up the style select popup, but pressing Shift-F3 again doesn't close it at all.
So send_key_until_needlematch doesn't work.

#6 Updated by openqa_review 3 months ago

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

This bug is still referenced in a failing openQA test: yast2_gui
https://openqa.suse.de/tests/9898912#step/yast2_control_center/1

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" or "EOL" (End-of-Life)
  3. 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.

#8 Updated by openqa_review 2 months ago

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

This bug is still referenced in a failing openQA test: yast2_gui@ppc64le-2g
https://openqa.suse.de/tests/10029289#step/yast2_snapper/1

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" or "EOL" (End-of-Life)
  3. 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.

#9 Updated by rainerkoenig 2 months ago

  • Status changed from In Progress to Closed

#10 Updated by rainerkoenig 2 months ago

  • Status changed from Closed to Resolved

#11 Updated by JERiveraMoya about 2 months ago

  • Parent task set to #121876

#12 Updated by JRivrain about 1 month ago

  • Status changed from Resolved to Workable
  • Assignee deleted (rainerkoenig)

Now causing different issue: https://openqa.suse.de/tests/10226822#step/iscsi_client/71: the key "ret" is not received by SUT... maybe send_key_until_needlematch could work ?
Reopening.

#13 Updated by dzedro about 1 month ago

JRivrain wrote:

Now causing different issue: https://openqa.suse.de/tests/10226822#step/iscsi_client/71: the key "ret" is not received by SUT... maybe send_key_until_needlematch could work ?
Reopening.

send_key_until_needlematch would probably work, but could get messy because the style window is not intended.
Just waiting for yast window to render works well.
https://github.com/os-autoinst/os-autoinst-distri-opensuse/pull/16180

#14 Updated by JRivrain about 1 month ago

  • Assignee set to JRivrain

#15 Updated by JERiveraMoya about 1 month ago

  • Status changed from Workable to In Progress

#16 Updated by JERiveraMoya about 1 month ago

  • Status changed from In Progress to Resolved
  • Assignee changed from JRivrain to rainerkoenig

@JRivrain, let's file a different ticket next time to follow our Yam process.
Resolving.

Also available in: Atom PDF