-
Notifications
You must be signed in to change notification settings - Fork 18k
all: 'go vet std cmd' no longer passes #37030
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
Thanks for catching this @josharian. I can reproduce on master. There are two parts to this. We should fix the vet issues. Additionally, we used to have a misc-vet-vetall builder. As far as I can tell, it was transformed into a test that runs by all.bash in issue #31916. However, all.bash didn't catch this regression. I filed issue #37053 to investigate why the builders didn't catch this and fix them. |
@mvdan, I may be missing something, but why do you think this is related to https://go-review.googlesource.com/c/go/+/162237? A lot of the lines it's flagging haven't changed in years... Why is it flagging them now? |
@aclements my bad - I got confused between the compiler's The code to decide what vet analyzers are enabled by default seems to have changed a couple of times around December, such as in https://go-review.googlesource.com/c/go/+/210937. Perhaps a regression was introduced around then. |
This may be related to the fix for #35837. I'm not sure that it is wrong, though: invoking |
Yeah, this is probably from CL 210937. We had not been setting |
Change https://golang.org/cl/217897 mentions this issue: |
Using Go 1.13.7,
go vet std cmd
passes cleanly. Using tip, it fails.This is a regression, so I'm tentatively marking as release-blocker.
The text was updated successfully, but these errors were encountered: