-
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: add LUCI netbsd-arm64 builder #63614
Comments
I assume |
cc @golang/release |
@bsiegert Yes, |
Sorry for the misunderstanding then. New CSR: netbsd-arm64-bsiegert.csr.txt |
Here is the certificate. |
The swarming bot is now running on one machine. Are you able to see it? Edit: https://chromium-swarm.appspot.com/bot?id=netbsd-arm64-bsiegert |
Yep! Unfortunately it seems to believe that its CPU architecture is |
Haha! In NetBSD terminology, the port is called In Python, you can get these names as follows:
On the 32-bit ARM builder, you instead get:
From http://wiki.netbsd.org/ports/evbarm/:
|
So for the ones Go cares about:
|
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>
Now that the swarming bot is correctly reporting https://ci.chromium.org/ui/p/golang/g/port-netbsd-arm64/builders It's passing on release-branch.go1.20 and many golang.org/x repos, and reporting failing tests at tip. I think we can close this tracking issue since the builder is up and use new issues for everything else. Thanks very much @bsiegert! |
Hostname: rpi4.bentsukun.ch
rpi4.bentsukun.ch.csr.txt
There are two machines in this builder. Should I add a second CSR for the other one, or should they share a hostname and CSR?
The text was updated successfully, but these errors were encountered: