-
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/build: linux-arm-arm5spacemonkey persistently broken #29177
Comments
For the record, if I remembered correctly, that builder is special in that it does cross compilation. The toolchain and the standard library is built on AMD64 machine(s) then shipped to the ARMv5 machine(s) to run the tests. When @rsc implemented the build cache, it would never work in this setting (failure was probably toolchain2 and toolchain3 were different). (And it is not possible to run everything on the ARMv5 machine because it is too slow.) So we decided to set up a toolchain version, to bypass certain checks. |
Seems like a duplicate of #24754, initially titled |
I'm happy to help if there is something we can do on the builders to make this easier. |
Is this resolved now? Or is this timeout issue masking it? This is from one of the latest test runs (https://build.golang.org/log/5137b5ef408a5c5a56d13ae902fe833f501d1e12):
|
Change https://golang.org/cl/162540 mentions this issue: |
…UT_SCALE So slow builders can finish their cgo tests, etc. Updates golang/go#29177 etc Change-Id: If5ee8d2201dc53ab506d4f5e31406d6aae240352 Reviewed-on: https://go-review.googlesource.com/c/162540 Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Dmitri Shuralyov <dmitshur@golang.org>
This builder is still persistently broken. Now it appears to be ignoring the From https://build.golang.org/log/4728fbb67eb490e9f3df8c5553e16c14fc7cfaf2:
|
Agreed. Also #24789. |
The linux-arm-arm5spacemonkey builder has been broken for as far back as I dared to page through the logs. It seems to be the only all-red (#22689) builder in the “first-class ports” view (#27689).
As far as I can tell, it's a configuration issue: for some reason the builder sets the Go version to
builder host-linux-armel-cross
instead of a more realistic version string, and that somehow causes the API check to fail.See previously #28041. (CC @bradfitz, @onionjake, @zeebo, @dmitshur )
Sample: https://build.golang.org/log/32dafc31f49b66f75902acd5f0d61cb8f6277de6
The text was updated successfully, but these errors were encountered: