action #95746
Updated by okurz over 2 years ago
## Motivation Using [openqa-investigate](https://github.com/os-autoinst/scripts/blob/master/README.md#openqa-investigate---automatic-investigation-jobs-with-failure-analysis-in-openqa) one can identify the root cause for failed tests. One cause could be "sporadic" openQA test issues which can (among other symptoms) be identified if the "retry" job triggered by openqa-investigate passes after the original job failed. We could feed back this information automatically to the original job as soon as the "retry" job finished ## Acceptance criteria * **AC1:** There is information present on the job details page of the original failed job if an issue is likely "sporadic" or not ## Suggestions * Extend openqa-investigate to instead of ignoring investigation jobs themselves in https://github.com/os-autoinst/scripts/blob/master/openqa-investigate#L11 instead detect them, identify ":retry:" ones and provide a comment back on the original job (e.g. follow the URL in the openQA setting for OPENQA_INVESTIGATION_ORIGIN, see (see #95742) about the result of retry if the original issue is likely sporadic or not * Alternative to "openqa-investigate" would be another, dedicated script or putting that functionality directly within openQA