-
Notifications
You must be signed in to change notification settings - Fork 1.2k
🏃 don't use apidiff on dirty commits #910
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
Conversation
2e4e855
to
f96088b
Compare
/assign @joelanford |
Is this because it's running during |
Yeah, exactly. I didn’t double check if it was the apidiff binary itself making the tree dirty or something else, but I figure this is fine either way. |
I thought it might be because of make test, but they're in separate containers on prow so that can't be it. My other two thoughts are either it's because the binary is built under the git path which makes it dirty or it's something due to how prow checks it out (I looked at that code and nothing stood out immediately). Either way, I figure we can add logging and try to force it through. We can at least ensure it's running against the right commits and figure out why it fails in the future. |
/test pull-controller-runtime-apidiff-master |
2 similar comments
/test pull-controller-runtime-apidiff-master |
/test pull-controller-runtime-apidiff-master |
af49f80
to
7031917
Compare
6a27aab
to
1b7e789
Compare
Would've helped to test on the right branch -_- was wondering why prow wasn't retesting for me The issue was with go.sum. I guess Go changed a crypto library out under us? I left the |
fixes #681 |
@alexeldeib @vincepri FYI, not sure this is related, but I have noticed some cases where go-apidiff will leave the git tree in a dirty state when it is finished. I haven't had the time to dig into why that happens, but if you notice that, let me know and we can dig deeper. |
/lgtm |
/approve |
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.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alexeldeib, vincepri 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 |
ref #909 (comment)