-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Disable vet
as part of go test
#33662
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
Conversation
`go vet` implicitely runs as part of `go test`, but we already have `make lint-go-vet`. Ref: https://pkg.go.dev/cmd/go#hdr-Test_packages
Actually I see we ran
So I've added a command that now runs plain |
Need to check whether |
On a lower powered machine this definitely helps. |
Yeah I agree, |
Before this can merge, I need to know whether @techknowlogick or @yp05327 do you perhaps know? |
Actually I was able to confirm that
So it needs to run it twice and the current approach is fine. |
Actually I found out we were still running it twice because regular Line 15 in b684f51
So I removed the explicit call to |
Also I've moved the flag to |
* giteaofficial/main: Disable `vet` as part of `go test` (go-gitea#33662) Refactor error system (go-gitea#33771) Add migrations and doctor fixes (go-gitea#33556) Refactor mail code (go-gitea#33768) Refactor global init code and add more comments (go-gitea#33755)
go vet
implicitely runs as part ofgo test
, but we already havemake lint-go-vet
, so we were essentially running it twice. This should hopefully makego test
slightly faster.Ref: https://pkg.go.dev/cmd/go#hdr-Test_packages