-
Notifications
You must be signed in to change notification settings - Fork 18k
x/tools/go/analysis: test failures due to disabled cgo with external linking #62268
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
Found new dashboard test flakes for:
2023-08-24 16:41 android-386-emu tools@c28af0ab go@d5c58085 x/tools/go/analysis/passes/tests.TestRunDespiteErrors (log)
2023-08-24 16:41 android-amd64-emu tools@c28af0ab go@d5c58085 x/tools/go/analysis/passes/tests.TestRunDespiteErrors (log)
|
Change https://go.dev/cl/522795 mentions this issue: |
Found new dashboard test flakes for:
2023-08-25 17:48 android-386-emu tools@c51e3f73 go@e92c0f84 x/tools/go/analysis/passes/tests.TestRunDespiteErrors (log)
2023-08-25 17:48 android-386-emu tools@c51e3f73 go@e92c0f84 x/tools/go/analysis/passes/tests.TestAnalysistest (log)
2023-08-25 17:48 android-386-emu tools@c51e3f73 go@e92c0f84 x/tools/go/analysis/passes/tests.TestMultichecker (log)
2023-08-25 17:48 android-386-emu tools@c51e3f73 go@777e65fe x/tools/go/analysis/passes/tests.TestRunDespiteErrors (log)
2023-08-25 17:48 android-386-emu tools@c51e3f73 go@777e65fe x/tools/go/analysis/passes/tests.TestAnalysistest (log)
2023-08-25 17:48 android-386-emu tools@c51e3f73 go@777e65fe x/tools/go/analysis/passes/tests.TestMultichecker (log)
2023-08-25 17:48 android-amd64-emu tools@c51e3f73 go@e92c0f84 x/tools/go/analysis/passes/tests.TestRunDespiteErrors (log)
2023-08-25 17:48 android-amd64-emu tools@c51e3f73 go@e92c0f84 x/tools/go/analysis/passes/tests.TestAnalysistest (log)
2023-08-25 17:48 android-amd64-emu tools@c51e3f73 go@e92c0f84 x/tools/go/analysis/passes/tests.TestMultichecker (log)
2023-08-25 17:48 android-amd64-emu tools@c51e3f73 go@777e65fe x/tools/go/analysis/passes/tests.TestRunDespiteErrors (log)
2023-08-25 17:48 android-amd64-emu tools@c51e3f73 go@777e65fe x/tools/go/analysis/passes/tests.TestAnalysistest (log)
2023-08-25 17:48 android-amd64-emu tools@c51e3f73 go@777e65fe x/tools/go/analysis/passes/tests.TestMultichecker (log)
|
Found new dashboard test flakes for:
2023-08-25 18:47 android-386-emu tools@5fb106a9 go@e92c0f84 x/tools/go/analysis/unitchecker (log)
2023-08-25 18:47 android-amd64-emu tools@5fb106a9 go@e92c0f84 x/tools/go/analysis/unitchecker (log)
|
Change https://go.dev/cl/523076 mentions this issue: |
Found new dashboard test flakes for:
2023-08-25 19:23 android-amd64-emu tools@2191a27a go@e92c0f84 x/tools/go/analysis/unitchecker (log)
|
Found new dashboard test flakes for:
2023-08-25 19:23 android-386-emu tools@2191a27a go@e92c0f84 x/tools/go/analysis/unitchecker (log)
|
@bcmills I just recognized go builds for android started to require CGO_ENABLED=1 since i have moved from 1.21.7 to 1.22.4: Do you know something about it? See open-telemetry/opentelemetry-collector#10516 |
We have tried various approaches in testenv.hasTool to detect whether 'go build' works without actually building a binary. However, they all turn out to be fairly fragile. If cgo is enabled then we need a C linker, but if the platform requires external linking then cgo must be enabled too. Instead of trying to second-guess whether 'go build' will actually work, let's just ask it to build a binary and see whether it succeeds. Hopefully this appreach will be simple enough in practice. This parallels the approach taken in CL 492979. Fixes golang/go#62268. Updates golang/go#46330. Change-Id: I9fd85fb73d291306e7bfb2f3ef6cf75a09cb6bed Reviewed-on: https://go-review.googlesource.com/c/tools/+/522795 Run-TryBot: Bryan Mills <[email protected]> Auto-Submit: Bryan Mills <[email protected]> TryBot-Result: Gopher Robot <[email protected]> Reviewed-by: Michael Matloob <[email protected]> gopls-CI: kokoro <[email protected]>
Issue created automatically to collect these failures.
Example (log):
— watchflakes
The text was updated successfully, but these errors were encountered: