-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Fix to handle exit code of gazelle command in hack/verify-bazel.sh #10182
Fix to handle exit code of gazelle command in hack/verify-bazel.sh #10182
Conversation
Hi @h3poteto. Thanks for your PR. I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
When some diff are detected in gazelle, the command exit(1), so verify-bazel.sh exit without any messages
0eaef05
to
51aadf1
Compare
/ok-to-test |
With this fix, the command output look like this:
|
Thanks @h3poteto - well found! /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: h3poteto, 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 |
I fix a script for development.
When some diff are detected in
gazelle
, the command exit(1), soverify-bazel.sh
exit without any messages.For example, I run
gazelle
command directly:And I run
hack/verify-bazel.sh
in the same condition:Because
gazelle
command exits with exit code 1 when it detects some diff, buthack/verify-bazel.sh
didn't handle the exit code ofgazelle
command.