You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The importer.ForCompiler function was added yesterday in https://golang.org/cl/152258. The vet test runs go build golang.org/x/tools/go/analysis/cmd/vet. Is it possible that your sources do not have importer.ForCompiler but the builder does have an up to date golang.org/x/tools? That is, do you just need to git codereview sync?
Is it possible that your sources do not have importer.ForCompiler but the builder does have an up to date golang.org/x/tools?
Oh, yes, I think that's probably it.
PS1 had the failure; PS2 (PS1 rebased at master) did not have it; but then I uploaded PS1 with tweaks (and without rebasing locally) as PS3 and had the failure again.
I've trybotted golang.org/cl/152544 three times, and twice it gave the same misc-vet-vetall failure:
https://storage.googleapis.com/go-build-log/5004c83e/misc-vet-vetall_2594bb0d.log
https://storage.googleapis.com/go-build-log/0ce4e24a/misc-vet-vetall_d4638ddb.log
I'm pretty sure these failures are unrelated to the CL, so maybe the trybot is broken?
/cc @bradfitz
The text was updated successfully, but these errors were encountered: