action #92188
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
test reviewers are pointed to the "first bad vs. last good" comparison if current job is not already the first bad
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. We already have a link to the "first bad" in investigation data but I suggest we provide a more prominent notice within the investigation tab if the current job is not the "first bad"
Acceptance criteria¶
- AC1: Investigation tab provides a notice pointing to "first bad"
Suggestions¶
- Research how #91521 was done and provide something more prominent in the UI, maybe a bootstrap info box? See https://www.w3schools.com/bootstrap/bootstrap_alerts.asp
Updated by okurz over 3 years ago
- Copied from action #91521: link to "first bad" in investigation tab added
Updated by tinita over 3 years ago
- Status changed from Workable to In Progress
- Assignee set to tinita
Updated by okurz over 3 years ago
- Copied to action #92731: clickable git log entries in investigation tab added
Updated by tinita over 3 years ago
Adding the box was the easy part.
I'm still fighting with adding a test in t/ui/18-tests-details.t. For that I have to find (or add) a test that actually has a "first_bad" test.