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
cmd/go: add -tags to go vet #10228
Comments
Your subject line suggests that you are using build tags. Please give us a complete example that we can use to recreate the problem. Thanks. (Looks like issue #4906 but that was meant to be fixed.) |
It's honoring the build tags, so it's not really a bug. But it should accept a -tags argument, like go build. |
-tags is one of the 'build flags' but we don't want all of them. |
CL https://golang.org/cl/10692 mentions this issue. |
This is needed to control which files to test in the usual manner. A followup CL on the main repo will add the flag to the go vet command. Updates golang/go#10228 Change-Id: I820d3c74657b58de5e92276627368dedf4e2096c Reviewed-on: https://go-review.googlesource.com/10692 Reviewed-by: Andrew Gerrand <adg@golang.org>
CL https://golang.org/cl/10697 mentions this issue. |
💃 Thank you @robpike! |
1.4.2
OS X
I just ran
go vet -x
on my packageI'm expecting to see 3 files being checked.
$ go vet -x
/usr/local/Cellar/go/1.4.2/libexec/pkg/tool/darwin_amd64/vet account.go account_test.go postgres.go
Only 2 files being checked.
The text was updated successfully, but these errors were encountered: