-
Notifications
You must be signed in to change notification settings - Fork 17.6k
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: add LUCI netbsd-arm builder #63698
Comments
Any updates? It's been a month. |
Thanks for pinging; it looks like we missed this new-builder issue, sorry. We'll pick this up at the start of next week since this week is short due to US holidays. |
Change https://go.dev/cl/545536 mentions this issue: |
For golang/go#63698. For golang/go#63614. For golang/go#64176. Change-Id: I2a203cd2a1e2e80ee44cfd5ce11c1ce5bbd60002 Reviewed-on: https://go-review.googlesource.com/c/build/+/545536 Reviewed-by: Heschi Kreinick <heschi@google.com> TryBot-Bypass: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org>
Here's the resulting certificate: netbsd-arm-bsiegert-1701367164.cert.txt. The builder definitions have been added in CL 545536 so your bot should be able to connect once you follow the rest of the steps on your end. We have some more work to do to make the dependencies built for the netbsd/arm port and available in CIPD, which will be needed for the builds to complete successfully. We'll update this issue once that's done. |
I mailed crrev.com/c/5086069 for this. |
That CL is submitted and the dependencies are built. If you give it a shot to connect with the builder, we can see what the next steps are for this. |
Thanks Dmitri! The bot is now up and running at https://chromium-swarm.appspot.com/bot?id=netbsd-arm-bsiegert. It shows up as |
Sorry, hit Submit too fast. It shows up as
|
I'm not seeing successful builds in https://ci.chromium.org/ui/p/golang/builders/ci/gotip-netbsd-arm?limit=200, and the builder isn't showing up as connected now. Can you take a look at what its current status is? I'll reopen this issue so we can track what's still left to do here. |
Change https://go.dev/cl/558517 mentions this issue: |
Handle another way in which cipd_platform is slightly different from Go's GOHOSTOS and GOHOSTARCH values. For golang/go#65241. For golang/go#63698. For golang/go#63601. Change-Id: I3caad897b821208939b8b411663ba417c4c21df7 Reviewed-on: https://go-review.googlesource.com/c/build/+/558517 TryBot-Bypass: Dmitri Shuralyov <dmitshur@golang.org> Reviewed-by: Michael Knyszek <mknyszek@google.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org>
CL 558517 fixed the
We need to figure out what's causing that and fix it to make progress here. Edit: I think https://source.chromium.org/chromium/infra/infra/+/main:luci/client/cipd.py;l=245 is the relevant line. The check for exit_code happens slightly later, on line 260, so it's possible something went wrong during the invocation of |
In addition to trying to reproduce this by running |
Thanks for the pointers, I will take a look and report back. |
This from
So the |
Downloading the Go binary from here and ranning
So it is built with GOARM=6 now (even though cross-compilation default for GOARM is 7 as of Go 1.21.). Searching finds entries like this, this, and this that all suggest making a change isn't quite straightforward, because the "v6l" suffix of the "netbsd-armv6l" CIPD platform dimension corresponds to GOARM=6. Maybe it's possible to make it work with GOARM=6 anyway, If the builder for this port cannot work with GOARM=6 binaries and really needs GOARM=7, we can see how involved that might be. |
I wonder why the Chromium infra thinks the architecture is "armv6l". That's a different sub-architecture. On this machine, FWIW, http://wiki.netbsd.org/ports/evbarm/ shows the different sub-architectures. This comment says:
Which is clearly a wrong assumption. |
Hostname: netbsd-arm-bsiegert
netbsd-arm-bsiegert.csr.txt
/cc @golang/release
The text was updated successfully, but these errors were encountered: