action #106909
closedcoordination #91646: [saga][epic] SUSE Maintenance QA workflows with fully automated testing, approval and release
coordination #98457: [epic] Handle openqa-review reminder comments on very old jobs better
[openqa-review] reminder comments point to specific openQA test details steps or openQA comments size:M
0%
Description
Motivation¶
As a ticket reader encountering openqa-review reminder comments I want to know which specific openQA test details step or needle triggered a reminder comment so that I can better fix the issue and prevent the reminder
Acceptance criteria¶
- AC1: The openqa-review reminder comments point to the specific openQA test detail step or comment that triggered a reminder comment
Suggestions¶
- Extend the reminder comments to state where exactly the ticket reference comes from, at best point the step detail in openQA
- For reminder comments triggered by openQA comments (mostly failed jobs, not softfailed) inform about that specifically as well
- Alternatives: Specific code location or the workaround needle in the git repo that references a ticket. For reference, the autoinst-log.txt has a line
[2022-02-08T11:34:07.525532+01:00] [debug] needle 'generic-desktop-test-20220206' is a workaround. The reason is bsc#123456
Updated by livdywan over 2 years ago
- Subject changed from [openqa-review] reminder comments point to specific openQA test details steps or openQA comments to [openqa-review] reminder comments point to specific openQA test details steps or openQA comments size:M
- Description updated (diff)
- Status changed from New to Workable
Updated by jbaier_cz over 2 years ago
- Status changed from Workable to In Progress
Updated by jbaier_cz over 2 years ago
I drafted a PR which adds logic to include steps from failures. Now, I am investigating another mentioned options (needles, comments).
Updated by jbaier_cz over 2 years ago
- Status changed from In Progress to Feedback
The PR is now merged, now we need to wait for results and evaluate.
Updated by jbaier_cz over 2 years ago
One such comment: https://progress.opensuse.org/issues/100940#note-18
Updated by jbaier_cz over 2 years ago
- Status changed from Feedback to Resolved
And also one in bugzilla: https://bugzilla.suse.com/show_bug.cgi?id=1194208#c11
I assume the feature is working.