-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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
go/internal/srcimporter: failure in TestImportStdLib and TestImportCgo with exit status 1
on linux-s390x-ibm
#52407
Comments
At the very least, that error message needs to be improved to explain what exited with The That implies that |
OTOH, I don't see any use of And, indeed, it has the potential to return a raw |
I suspect that this particular failure mode is due to a platform or |
Change https://go.dev/cl/400817 mentions this issue: |
An error message like "could not import os/user (exit status 1)" (observed in https://go.dev/issue/52407) is fairly inscrutable. On the other hand, srcimporter doesn't report errors with quite enough structure to dump the entire stderr output from 'go tool cgo' without potentially overwhelming the caller. Here, we split the difference by describing which command failed but not printing the output of that command. For #52407, that would at least provide a stronger clue connecting to #52408. Change-Id: Iabdc95b17ba20a0f6ff38e5c7084e5081e1ef5e8 Reviewed-on: https://go-review.googlesource.com/c/go/+/400817 Run-TryBot: Bryan Mills <bcmills@google.com> Reviewed-by: Matthew Dempsky <mdempsky@google.com> Auto-Submit: Bryan Mills <bcmills@google.com> TryBot-Result: Gopher Robot <gobot@golang.org>
I should have closed this earlier. It was the same issue as #52408. Reinstalling the gcc-c++ and related packages at the correct versions on the builder fixed this issue back on Apr 18. |
greplogs --dashboard -md -l -e 'FAIL: Test(?:ImportStdLib|Cgo) .*(?:\n .*)exit status 1' --since=2022-01-01 --omit=.\*-n2d
2022-04-17T01:33:13-740a490/linux-s390x-ibm
The text was updated successfully, but these errors were encountered: