Project

General

Profile

Actions
Copy link

coordination #91518

closed

coordination #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

[epic] Provide 'first bad' vs. 'last good' difference in investigation info

Added by okurz over 3 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
okurz
Category:
Feature requests
Target version:
Ready
Start date:
2021-04-21
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)

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.

Acceptance criteria

  • AC1: test reviewers are pointed to the "first bad vs. last good" comparison if current job is not already the first bad

Subtasks 2 (0 open — 2 closed)

action #91521: link to "first bad" in investigation tabResolvedosukup2021-04-21

Actions
action #92188: test reviewers are pointed to the "first bad vs. last good" comparison if current job is not already the first badResolvedtinita

Actions
Actions
Copy link
 #1

Updated by okurz over 3 years ago

  • Status changed from Blocked to Resolved

Both subtasks resolved. I consider the current way with a highlighting popup box pointing to the "first bad" in bold font as good approach.

Actions
Copy link

Also available in: Atom PDF