-
Notifications
You must be signed in to change notification settings - Fork 18k
cmd/go: add -tests to list of vet checks run by "go test" #44251
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
Comments
Is at least correctly reported on the playground https://play.golang.org/p/dj_FUdOxN1j |
The problem is reported by |
@D1CED Ah, I thought it isn't relevant to playground, my guess was wrong. @ianlancetaylor I keep forget about |
Yes, I'll change this issue into a proposal to do that. |
Great, thank you. |
Perusing the source of the |
Change https://go.dev/cl/529816 mentions this issue: |
@adonovan to run ecosystem metrics pipeline analysis to make sure there aren't false positives in the broader Go ecosystem. |
This proposal has been added to the active column of the proposals project |
Very nice! Are there any remaining concerns about this proposal? |
Based on the discussion above, this proposal seems like a likely accept. The proposal is to run ‘go vet -tests’ automatically during ‘go test’, with the many other vet checks that run then. |
No change in consensus, so accepted. 🎉 The proposal is to run ‘go vet -tests’ automatically during ‘go test’, with the many other vet checks that run then. |
Change https://go.dev/cl/603476 mentions this issue: |
What version of Go are you using (
go version
)?go 1.15.8
What did you do?
I resturctured my test TestXXX as an example ExampleXXX. But forgot to remove the argument.
What did you expect to see?
ExampleXXX(t *testing.T) is wrong signature for an example (has *testing.T as an argument),
so it should raise error on
go test
.What did you see instead?
It didn't run. Made me assumes the test has successfully finished.
The text was updated successfully, but these errors were encountered: