cmd/go: building a test binary with "go test -c" probably shouldn't run vet #32134
While working on some slow full emulation qemu VMs, I noticed
It seems surprising that we default to running vet on a flag that's described as:
Any vet output would look like a test failed and thus ran, even if it's not technically a test.
In any case, it's not critical. Now I know to always use
Marking for Go 1.14, unless this is a recent regression. I didn't check.
The trouble with turning off the
I understand why this is surprising, but — especially given the
@bcmills given that the standard way to run a package's tests is
Perhaps one user or machine could unintentionally ignore vet for a bit, but I imagine other machines or humans would quickly start seeing the vet warnings.
I don't think we should be telling people who really just want