-
-
Notifications
You must be signed in to change notification settings - Fork 662
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
aux_files
incorrect behavior in source gomocks
#3752
Comments
ikavalio
added a commit
to ikavalio/rules_go
that referenced
this issue
Nov 14, 2023
I'm sorry for combining two different things into a single issue:
just as a side note, the issue is still valid for |
I submitted a pr #3753 for the diff above, but feel free to reject it if it makes no sense. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What version of rules_go are you using?
0.42.0
What version of gazelle are you using?
0.32.0
What version of Bazel are you using?
6.4.0
Does this issue reproduce with the latest releases of all the above?
yup!
What operating system and processor architecture are you using?
darwin/arm64, but I can reproduce it on linux/amd64 too
Any other potentially useful information about your toolchain?
the issue can be reproduced on the go toolchain with cgo/cross-compilation disabled
What did you do?
If we add the following code to the gomock rule test suite:
The
bazel build //tests/extras/gomock:wrapper_mocks
will legitimately fail withmockgen
needs theclient.go
in the bazel'sgopath
and the only method to do it hermetically right now is to useaux_files
like this:Which is what I'm currently trying to do.
What did you expect to see?
bazel build //tests/extras/gomock:wrapper_mocks
works andbazel test //tests/extras/gomock:client_test
passes, when the changes above are applied.What did you see instead?
Further details
I think the following patch to the
gomock
rule fixes the issue:I can convert it to the PR if it looks alright.
The text was updated successfully, but these errors were encountered: