action #98862
Updated by okurz about 2 years ago
## User story When a job fails, we will investigate the job by triggering new job with different conditions, such as rerun, re-run with last good build, or last commit in the test distribution. commit. If a retry the rerun job passes, the original origin job may be a intermittent/sporadic sporadic case. If the last good build rerun job passes, there may be a product issue. We should provide that assessment as a can comment back on these useful message to the original origin job. ## Acceptance criteria * **AC1:** If an openqa-investigate retry job passes a according to the investigation result, comment is created on the original back to origin job with the assessment that the issue is intermittent or a sporadic test issue ## Suggestions * Take a look how we identify likely sporadic issues as a result of *failed* "retry" jobs in https://github.com/os-autoinst/scripts/blob/master/openqa-investigate#L136= Consider use minion task * Extend to react according on *passed* retry Here is an investigation: https://github.com/os-autoinst/openQA/pull/4206 ## Further details * Ensure <everything that hook scripts in github.com/os-autoinst/scripts/ act as one should expect when called on *passed* jobs * Extend o3 config to also run job_done_hooks on passed jobs and monitor performance impact * Same on osd as on o3 does not fit into above sections>