cmd/vet: Go vet misses error when running in shell and not Makefile #21688
Labels
Milestone
Comments
Note that |
I did try with go tool vet.
|
We need to see the exact commands and input files to reproduce the problem. It's extremely unlikely that it has anything to do with being run from a Makefile. It's much more likely that it has to do with exactly how the Makefile runs the command. |
I'm a total dunce. It's the Thanks @ianlancetaylor |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
What version of Go are you using (
go version
)?Tested on:
and
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?Additionally, I'm running in ZSH, although the issue isn't caught in bash either.
What did you do?
Trying to reproduce in a pruned makefile I couldn't reproduce it. I'll see about cleaning up the actual makefile which reproduces the issue.
What did you expect to see?
Vet catch the error running from the command line.
What did you see instead?
Vet doesn't catch the error from the command line.
I'll continue to try to reproduce in different environments / in isolation so it can hopefully be reproduced by others. Otherwise, I'll just continue to go insane. :-)
Lemme know if there's anything easy I can do to get more visibility into the program, before I dig too deeply into it.
The text was updated successfully, but these errors were encountered: