-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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
x/tools/refactor/importgraph: TestBuild is failing sometimes #37823
Comments
Have these failures been occurring at a particular version of Go? This package uses go/build to get its information so I'm guessing the failures are related to that. Maybe there's been a in go/build or cmd/go that's causing this. I wonder if it has to do with the test not setting GO111MODULE=off... |
Change https://golang.org/cl/367846 mentions this issue: |
Marking as release-blocker for Go 1.18 via #11811. I have what I believe to be a fix CL pending. |
…rs from Build This test was written for GOPATH mode, and subsequently updated to use packagestest at a time when GO111MODULE defaulted to "auto" (in this case, off). As a result, the test was failing to set environment variables relevant to the test, such as GO111MODULE=off. The missing environment was causing errors that were subsequently masked by a missing error check: the errors returned by importgraph.Build were only read in an "if false" block. This CL adds the missing environment variables and error checks. Using the correct environment may or may not fix the observed test failures. For golang/go#37823 Change-Id: I75844e6fdf47222aa4f953c8c4fbcc93cec606c9 Reviewed-on: https://go-review.googlesource.com/c/tools/+/367846 Trust: Bryan C. Mills <bcmills@google.com> Run-TryBot: Bryan C. Mills <bcmills@google.com> Reviewed-by: Robert Findley <rfindley@google.com> gopls-CI: kokoro <noreply+kokoro@google.com> TryBot-Result: Go Bot <gobot@golang.org>
I'm seeing frequent failures that look like this at https://build.golang.org/?repo=golang.org%2fx%2ftools on the darwin builders:
For a recent example, see https://build.golang.org/log/5b156a1c79480768102921c27ab1b16ccc7c0590.
/cc @matloob
The text was updated successfully, but these errors were encountered: