mirror of https://github.com/golang/go.git
If cmd/compile is in an unhappy state, the testdir test can fail with an unhelpful 'exit code 1' log message if 'go list' fails while gathering stdlib import config When running individual files, such as: go test cmd/internal/testdir -run='Test/escape.*.go' This might also happen in other uses, or it might be that a more expansive set of tests such as run.bash might first trigger a more useful error. This change prints stderr and states that it is 'go list' that is having problems to help someone track down the proper issue. Change-Id: Iba658ea139bb9087ab8adb00c9f65080a1b6ee76 Reviewed-on: https://go-review.googlesource.com/c/go/+/524941 Reviewed-by: Matthew Dempsky <mdempsky@google.com> Reviewed-by: Than McIntosh <thanm@google.com> Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Russ Cox <rsc@golang.org> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> |
||
|---|---|---|
| .. | ||
| testdir_test.go | ||