-
Notifications
You must be signed in to change notification settings - Fork 38.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 some fixture path calculations #90872
Conversation
staging/src/k8s.io/apiextensions-apiserver/pkg/cmd/server/testing/testserver.go
Show resolved
Hide resolved
add a comment and a log message, then lgtm |
a711ac8
to
0deb7bd
Compare
Current calculations assume that -trimpath is not passed to go tool compile, which is not the case for test binaries built with bazel. This causes issues for integration tests right now but is generally not correct. The approach taken here is a bit of a hack but it works on the assumption that if and only if trimpath is passed, we are running under bazel. I didn't see a good spot for pkgPath(), so I just copied it around.
/retest |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: liggitt, mikedanese 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 |
/retest |
Current calculations assume that -trimpath is not passed to go tool
compile, which is not the case for test binaries built with bazel. This
causes issues for integration tests right now but is generally not
correct.
The approach taken here is a bit of a hack but it works on the
assumption that if and only if trimpath is passed, we are running under
bazel. I didn't see a good spot for pkgPath(), so I just copied it
around.
/kind bug
/sig testing