action #113758
opencoordination #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
0%
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.
Updated by okurz over 2 years ago
- Category set to Regressions/Crashes
- Target version set to Ready
Updated by okurz over 2 years ago
- Related to action #104007: Support retry of openQA jobs based on test variables added
Updated by AdamWill over 2 years ago
hum, after watching this a bit longer it seems not so straightforward. it seems like sometimes the retried job is marked as a clone of the original and sometimes it isn't. Not sure what causes the difference.
Updated by livdywan over 2 years ago
AdamWill wrote:
hum, after watching this a bit longer it seems not so straightforward. it seems like sometimes the retried job is marked as a clone of the original and sometimes it isn't. Not sure what causes the difference.
Would you have examples you can share? Maybe there is some subtle difference in job settings or the state of the job