Project

General

Profile

Actions

action #92188

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

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

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

Status:
Resolved
Priority:
Low
Assignee:
Category:
Feature requests
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:

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


Related issues 2 (0 open2 closed)

Copied from openQA Project (public) - action #91521: link to "first bad" in investigation tabResolvedosukup2021-04-21

Actions
Copied to openQA Project (public) - action #92731: clickable git log entries in investigation tabResolvedybonatakis

Actions
Actions

Also available in: Atom PDF