Project

General

Profile

Actions

action #161267

open

coordination #99303: [saga][epic] Future improvements for SUSE Maintenance QA workflows with fully automated testing, approval and release

coordination #155671: [epic] Better handling of SLE maintenance test review

Represent the effect of "@review:acceptable_for" labels on qem-dashboard pages size:M

Added by okurz 6 months ago. Updated 2 months ago.

Status:
Workable
Priority:
Normal
Assignee:
-
Target version:
Start date:
2024-05-30
Due date:
% Done:

0%

Estimated time:

Description

Motivation

https://github.com/openSUSE/qem-dashboard/ on pages like http://dashboard.qam.suse.de/blocked shows which updates are blocked but to find more details what decision qem-bot does and why certain incidents are still blocked it can be multiple clicks and digging through log files of qem-bot to find out the current status in details, in particular when using @review:acceptable_for:incident_X labels on openQA jobs which still represent as simply red boxes on the dashboard. For making the life of reviewers easier the dashboard should be able to provide more details, at best on all levels accordingly.

Additional explanation by mgrifalconi:

I fear you see something only the bot logs https://gitlab.suse.de/qa-maintenance/bot-ng/-/jobs for approve incident jobs
You should see something like
"Ignoring failed job %s for incident %s due to openQA comment"
https://github.com/openSUSE/qem-bot/blob/463d5de225767791d0b6815435a0b341ce319c67/openqabot/approver.py#L261
BUT only if there is no other genuine failure "found" by the bot first. In that case, the bot will give up at first non-ignored failure and won't look at other acceptable ones.
Or you can see that it goes out of the queue and gets approved eventually :smile:
Would be nice to reflect that on the dashboard though, since at first glance it looks like something was not reviewed when instead it was.

Ideas

I am thinking of two things to do:

  1. Provide the last relevant log lines referring to each incident on the page for each incident of the dashboard
  2. use another pattern and color for the "acceptable_for" result. I am thinking of a yellow-green dashed pattern in the background of each result box

Acceptance criteria

Suggestions

Actions #1

Updated by okurz 6 months ago

  • Parent task set to #155671
Actions #2

Updated by pcervinka 4 months ago

@okurz I understand that tools team is busy, but be would be possible to increase priority from low to something higher? This dashboard visibility issue makes regular confusion about maintenance update status.

Actions #3

Updated by okurz 4 months ago

  • Priority changed from Low to Normal
Actions #4

Updated by pvorel 4 months ago

Hint from Oliver (https://suse.slack.com/archives/C02DQJKULE4/p1722327940699429?thread_ts=1722235479.858789&cid=C02DQJKULE4):

https://github.com/openSUSE/qem-bot/blob/463d5de225767791d0b6815435a0b341ce319c67/openqabot/approver.py#L129 is where the "acceptable_for" comment in qem-bot is parsed and evaluated. The challenge is that this is called during the "approval" command which is not syncing anything to the dashboard (yet).

Actions #5

Updated by okurz 2 months ago

  • Target version changed from future to Tools - Next
Actions #6

Updated by okurz 2 months ago

  • Subject changed from Represent the effect of "@review:acceptable_for" labels on qem-dashboard pages to Represent the effect of "@review:acceptable_for" labels on qem-dashboard pages size:M
  • Description updated (diff)
  • Status changed from New to Workable
Actions

Also available in: Atom PDF