Skip to content
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

Merged
merged 1 commit into from
Jan 10, 2021

Conversation

h3poteto
Copy link
Contributor

@h3poteto h3poteto commented Nov 6, 2020

I fix a script for development.

When some diff are detected in gazelle, the command exit(1), so verify-bazel.sh exit without any messages.

For example, I run gazelle command directly:

$ _output/bin/gazelle fix -external=vendored -exclude=tests/e2e -mode=diff -proto=disable -repo_root=./
--- cmd/kops-controller/pkg/server/BUILD.bazel  1970-01-01 00:00:00.000000000 +0000
+++ cmd/kops-controller/pkg/server/BUILD.bazel  1970-01-01 00:00:00.000000000 +0000
@@ -13,9 +13,9 @@
         "//pkg/apis/nodeup:go_default_library",
         "//pkg/pki:go_default_library",
         "//pkg/rbac:go_default_library",
+        "//upup/pkg/fi:go_default_library",
         "//vendor/k8s.io/apimachinery/pkg/util/sets:go_default_library",
         "//vendor/k8s.io/klog/v2:go_default_library",
-        "//upup/pkg/fi:go_default_library",
     ],
 )
$ echo $?
1

And I run hack/verify-bazel.sh in the same condition:

$ hack/verify-bazel.sh
$ echo $? 
1

Because gazelle command exits with exit code 1 when it detects some diff, but hack/verify-bazel.sh didn't handle the exit code of gazelle command.

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Nov 6, 2020
@k8s-ci-robot
Copy link
Contributor

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 /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

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.

@k8s-ci-robot k8s-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Nov 6, 2020
When some diff are detected in gazelle, the command exit(1), so verify-bazel.sh exit without any messages
@h3poteto h3poteto force-pushed the fix/hack-verify-bazel branch from 0eaef05 to 51aadf1 Compare November 6, 2020 15:05
@hakman
Copy link
Member

hakman commented Nov 7, 2020

/ok-to-test

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Nov 7, 2020
@h3poteto
Copy link
Contributor Author

With this fix, the command output look like this:

$ hack/verify-bazel.sh
--- cmd/kops-controller/pkg/server/BUILD.bazel  1970-01-01 00:00:00.000000000 +0000
+++ cmd/kops-controller/pkg/server/BUILD.bazel  1970-01-01 00:00:00.000000000 +0000
@@ -13,9 +13,9 @@
         "//pkg/apis/nodeup:go_default_library",
         "//pkg/pki:go_default_library",
         "//pkg/rbac:go_default_library",
+        "//upup/pkg/fi:go_default_library",
         "//vendor/k8s.io/apimachinery/pkg/util/sets:go_default_library",
         "//vendor/k8s.io/klog/v2:go_default_library",
-        "//upup/pkg/fi:go_default_library",
     ],
 )


FAIL: ./hack/verify-bazel.sh failed, as the bazel files are not up to date
FAIL: Please execute the following command: ./hack/update-bazel.sh
$ echo $?
1

@justinsb
Copy link
Member

Thanks @h3poteto - well found!

/approve
/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 10, 2021
@k8s-ci-robot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 10, 2021
@k8s-ci-robot k8s-ci-robot merged commit ac082bd into kubernetes:master Jan 10, 2021
@k8s-ci-robot k8s-ci-robot added this to the v1.20 milestone Jan 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants