-
Notifications
You must be signed in to change notification settings - Fork 220
chore: make apidiff test more robust and informative #1542
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
chore: make apidiff test more robust and informative #1542
Conversation
* Use exec so that if the prow job is killed, the script is killed too * Print full apidiff output in both success and failure cases
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: justinsb The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
✅ Deploy Preview for kubernetes-sigs-cluster-api-gcp ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
I'm slightly at a loss as to why sometimes apidiff hangs for 50+ hours, I'm guessing the prow job is OOM killed or something like that. |
|
Confirmed an OOM kill in the prow description for the test: |
|
Also raising memory in kubernetes/test-infra#35686 to mirror apidiff CAPA jobs |
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.
Thanks @justinsb.
/lgtm
Uh oh!
There was an error while loading. Please reload this page.