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: failures with junk at end of line:
on linux-s390x-ibm
#52408
Comments
(attn @jonathan-albrecht-ibm) |
So far these failures are only happening on one of the builders (go02). I can reproduce it manually on go02 as well. It's not happening on the other builder (go01) either as part of the build farm builds or when I build and test manually. I've stopped the go02 builder service while I try and figure out what's going wrong. |
The problem with the go02 build seems to be because some of the gcc* packages were updated due to: https://go-review.googlesource.com/c/build/+/399996. I think it left the gcc toolchain in a bad state. I rolled back the updated packages and tested locally and everything worked again. I've restarted the buildlet service on go02 and I'll watch it for problems. I've left a comment on https://go-review.googlesource.com/c/go/+/336549/comments/eb61ef44_7b74dba0 and I'll try and get things set up properly on the current builders. I'll try and set up the new builders I'm provisioning to avoid this mess. |
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>
Sorry I should have closed this earlier. Reinstalling the gcc-c++ and related packages at the correct versions on the builder fixed this issue back on Apr 18. |
This error message is also seen in several other tests, probably from the same root cause.
greplogs --dashboard -md -l -e 'junk at end of line' --since=2022-01-01
2022-04-18T12:04:50-46bc274-91b9915/linux-s390x-ibm
2022-04-17T00:58:13-46bc274-e948c33/linux-s390x-ibm
2022-04-16T02:01:19-46bc274-5e4543c/linux-s390x-ibm
2022-04-15T23:25:46-46bc274-e398266/linux-s390x-ibm
The text was updated successfully, but these errors were encountered: