-
-
Notifications
You must be signed in to change notification settings - Fork 255
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
Creating regex logic for build autotriager #3576
Creating regex logic for build autotriager #3576
Conversation
As well as the logic to handle them, and some useful metadata. Also added some temporary git action logic to aid debugging. Will remove prior to the merge. Signed-off-by: Adam Farley <[email protected]>
Signed-off-by: Adam Farley <[email protected]>
Signed-off-by: Adam Farley <[email protected]>
As the regex also matches several warnings that are present in successful builds, so we stop trying to match errors before reaching the actual cause of failure. Signed-off-by: Adam Farley <[email protected]>
Signed-off-by: Adam Farley <[email protected]>
Signed-off-by: Adam Farley <[email protected]>
Signed-off-by: Adam Farley <[email protected]>
Signed-off-by: Adam Farley <[email protected]>
Signed-off-by: Adam Farley <[email protected]>
Signed-off-by: Adam Farley <[email protected]>
Signed-off-by: Adam Farley <[email protected]>
Signed-off-by: Adam Farley <[email protected]>
Signed-off-by: Adam Farley <[email protected]>
Resolving the linter failures now. |
Signed-off-by: Adam Farley <[email protected]>
The build failures cannot be related to this change because the build auto-triage scripts are not part of the build process. |
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
Though I won't add jdk23 because I'm not seeing a jdk23 pipeline yet. Signed-off-by: Adam Farley <[email protected]>
So peoples' personal repos don't get filled with triage issues. Re-added the push logic to test. Signed-off-by: Adam Farley <[email protected]>
Signed-off-by: Adam Farley <[email protected]>
Signed-off-by: Adam Farley <[email protected]>
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.
Approving based on the demo last week and the runs listed in the description which seemed to work. I have no done a full review of the code, but that can be revised later
Adds the logic and list of regexes that are used to determine the likely cause of a build's failure/aborted state.
Also identifies the likely cause of each failure, as well as whether it could have been prevented, and presents that information in a new git issue.
Example run here: https://github.com/adamfarley/temurin-build/actions/runs/7195461176
Example issue here: adamfarley#35
Resolves #3521