Project

General

Profile

coordination #91518

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 about 2 months ago. Updated 25 days ago.

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

100%

Estimated time:
(Total: 0.00 h)
Difficulty:

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

action #91521: link to "first bad" in investigation tabResolvedosukup

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

Also available in: Atom PDF