search

mesonbuild / meson-python

Meson PEP 517 Python build backend
https://mesonbuild.com/meson-python/
MIT License
125 stars 65 forks source link

BUG: use 11.0 as minimum macOS platform ABI tag on arm64 #527

Closed dnicolodi closed 10 months ago

dnicolodi commented 11 months ago

Fixes #524.

dnicolodi commented 10 months ago

The test failure is odd. I would have thought that packaging would refuse to generate a tag on macOS with an ABI version lower than 11.0 on arm64. I'll see if there is a more suitable packaging function to use in this test.

This highlights that we have a test coverage gap that we should fix (can be done later, I can test locally for now).

It mostly highlights that my laptop is still an Intel mac. We don't test on architectures other than amd64 for any other platform. Extending the CI to run on other architectures would be nice, but not very high priority.

dnicolodi commented 10 months ago

We're under the mesonbuild org, so it's not possible to see our credits usage on Cirrus CI - and hence I'm not sure if we can add arm64 on Cirrus. Meson itself doesn't use Cirrus though, so it seems like we can try without causing an issue; worst-case we'd exhaust free credits in one month.

AFAIK Cirrus CI does not use a credit system for using their service within the limits allocated to public repositories. https://cirrus-ci.org/faq/#are-there-any-limits So far we don't use any macOS worker on Cirrus CI so far, so we can setup one to run on arm64 and still have all the workers run in parallel

dnicolodi commented 10 months ago

Correction. The page I linked to actually reports that there is also a monthly usage cap. I don't think we are likely to hit the 10000 CPU minutes limit for Linux tasks, but the 500 minutes per month for macOS task is not very high. I'll setup the macOS arm64 jobs and see how we do.

dnicolodi commented 10 months ago

There does not seem to be a better packaging API to use for the test. I fixed it the ugly way. The macOS arm64 CI job seems to be running fine.