-
-
Notifications
You must be signed in to change notification settings - Fork 314
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Auto rerun test build in FAILURE status #5747
Conversation
Signed-off-by: Lan Xia <[email protected]>
TRSS: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Since I have no visibility of tests run on hyc Jenkins, from your testing, what is the difference between |
Signed-off-by: Lan Xia <[email protected]>
0196df6
to
eb338a6
Compare
Sorry, Grinder links expired. I think the second link has a typo. It is for scenario |
Public test runs: JDK11, x64Linux and ppc64Aix: JDK17, x86-32_windows,s390x_linux: JDK8, x64Linux: |
I do not quite think I got all of the AQA_Test_Pipeline parameters correct, as many of the test jobs failed with
But at least, it forced test job failures, which then triggered reruns which is the functionality that I hoped the runs would demonstrate. TRSS instance does not show the rerun link in the tooltip, but it has not been synched in a while, so perhaps that is why. It does show the info circle in the top corner of the chiclet in the Grid view though, indicating there was a rerun. |
re #5747 (comment), the rerun job was generated and triggered. https://ci.adoptium.net/job/Test_openjdk17_hs_extended.openjdk_s390x_linux/196/console However, Note: This PR (Step 1) does not cover rerun at the parent level (i.e., |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AQA_Test_Pipeline runs showed reruns were triggered for failed jobs.
This PR will auto-rerun the child test build in FAILURE status (Part 1). To enable this feature, params.RERUN_FAILURE needs to be true.
We will enable the parent test build of rerun in Part 2.
related: #5346