x/build: add LUCI netbsd-arm64 builder

[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?

[bsiegert]

I assume netbsd-arm64-bsiegert (matching the previous builder name) would be a better hostname for the CSR?

[cagedmantis]

cc @golang/release

[cagedmantis]

@bsiegert Yes, netbsd-arm64-bsiegert would be a better hostname for the CSR.

[bsiegert]

Sorry for the misunderstanding then. New CSR: netbsd-arm64-bsiegert.csr.txt

[dr2chase]

Here is the certificate.
netbsd-arm64-bsiegert-1698683802.cert.txt

[bsiegert]

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

[heschi]

Yep!

Unfortunately it seems to believe that its CPU architecture is evbarm, which is an exciting new way to spell arm64. Is there some Python 3 API we could call that would return arm64? Or do we need to map it ourselves?

[bsiegert]

Haha! In NetBSD terminology, the port is called evbarm-aarch64. evbarm is "ARM evaluation board".

In Python, you can get these names as follows:

>>> platform.processor()
'aarch64'
>>> platform.machine()
'evbarm'

On the 32-bit ARM builder, you instead get:

>>> platform.processor()
'earmv7hf'
>>> platform.machine()
'evbarm'

From http://wiki.netbsd.org/ports/evbarm/:

Various CPU variants are supported, e.g:

• earmv6hf - ARMv6-A with EABI and hardware floating point, e.g. the original Raspberry Pi.
  earmv7hf - ARMv7-A with EABI and hardware floating point, e.g. most recent and common 32-bit ARM boards. Supports up to 8 CPUs.
• earmv7hfeb - Same as the above, but with the CPU running in big endian mode.
• aarch64 - 64-bit ARMv8-A boards, e.g. all 64-bit hardware. Fully 64-bit kernel and userland. Running 32-bit binaries is supported with compat32.
• aarch64eb - Same as the above, but with the CPU running in big endian mode.