Project

General

Profile

Actions

action #113758

open

coordination #102906: [saga][epic] Increased stability of tests with less "known failures", known incompletes handled automatically within openQA

Jobs restarted with `RETRY` are not shown as 'clones', so it is hard or impossible find the original job

Added by AdamWill over 2 years ago. Updated over 2 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Regressions/Crashes
Target version:
Start date:
2022-07-18
Due date:
% Done:

0%

Estimated time:
Tags:

Description

I recently switched Fedora's openQA from using our own downstream automatically-retry-failed-jobs plugin to using the upstream RETRY behavior. One thing I've noticed: with our downstream plugin, which used $job->auto_duplicate, the new job was shown as a clone of the failed job. So, for instance, if the retry failed too, you could easily find the original job and see if it failed for the same reason.

With RETRY, it seems the retry is not considered a clone of the original, so there is no easy way to find the original job at all - there's no handy link in the web UI.


Related issues 1 (0 open1 closed)

Related to openQA Project (public) - action #104007: Support retry of openQA jobs based on test variablesResolvedokurz2021-12-15

Actions
Actions

Also available in: Atom PDF