Support ARM / M1 macOS in validate.sh

[9999years]

Previously, validate.sh would assume that all non-Linux and non-Windows builds were x86_64 macOS. ARM64 macOS and Linux machines (and, to an extent, Windows machines) are now quite common. The test suite should work with them.

[geekosaur]

Arguably we should be even more flexible, but I suspect that'll have to wait until we actually have people using e.g. risc-v (and, more importantly, CI resources for them).

[ulysses4ever]

Thank you! We'd welcome a contribution moving our Validate GitHub workflow to use arm runners that GitHub now provides. When they just appeared, our CI failed miserably, so we had to pin the intel runners.

[9999years]

You're welcome! Is there anything I need to do to get this merged?

[geekosaur]

This PR is ready; you need only set the label and Mergify will do the rest. Since it's only one commit, there's no practical difference between the "merge me" and "squash+merge me" labels.

(Mergify will wait two days to merge it, to allow for last minute comments or updates which will restart the timer.)

[geekosaur]

If you do decide to take on the M1 runner problem, you'll want to look over #9949 and #9948 for the issues we ran in to that caused us to force the Intel runners. Hopefully most of those problems have been resolved in recent versions of the macos-14 image. But that should be a separate PR.

[9999years]

@geekosaur I'm not a maintainer so I don't have permissions to edit PR labels, even my own.

[geekosaur]

Label set.

[Mikolaj]

@geekosaur I'm not a maintainer so I don't have permissions to edit PR labels, even my own.

@9999years: Thank you for the PR. I've invited you to the repo. If the Triage role is not enough to set labels, please let me know (but it should be IIRC).

[geekosaur]

It is, per GitHub's description of the roles here (not sure this is accessible to non-admins though, since it's under repository settings).

[9999years]

@Mikolaj Thank you, that'll make it easier for me in the future!