action #91521
closedcoordination #39719: [saga][epic] Detection of "known failures" for stable tests, easy test results review and easy tracking of known issues
coordination #19720: [epic] Simplify investigation of job failures
coordination #91518: [epic] Provide 'first bad' vs. 'last good' difference in investigation info
link to "first bad" in investigation tab
Description
Motivation¶
With the investigation tab on failed openQA jobs test reviewers can find the "last good" and the difference between the current job and the "last good". However in many cases the difference between the actual "first bad" vs. "last good" has a smaller difference and more relevant information. So we should at least provide a link to the "first bad" in investigation data
Acceptance criteria¶
- AC1: Investigation tab provides link to "first bad"
Suggestions¶
- Research how the "last good" is computed and extend to do the equivalent for "first bad"
Updated by osukup about 3 years ago
- Status changed from Workable to In Progress
Updated by okurz about 3 years ago
Nicely done. "Feedback" is correct as according to https://progress.opensuse.org/projects/qa/wiki#Definition-of-DONE we should wait to see that in production, e.g. tomorrow on o3.
Updated by osukup almost 3 years ago
- Status changed from Feedback to Resolved
no negative feedback, setting to done
Updated by okurz almost 3 years ago
- Copied to action #92188: test reviewers are pointed to the "first bad vs. last good" comparison if current job is not already the first bad added