Use of another CI provider for native linux_aarch64 and macosx_arm64
Hi all, I've been investigating the use of cirrus-ci for native building of wheels for linux_aarch64. Currently it takes about 2 hours to build a wheel on Github Actions using emulation, but on cirrus-ci it's about 5 minutes. This will enable us to fully test the wheels that are produced, rather than just a subset of tests. It would also be possible to build macosx_arm64 wheels natively rather than a cross compile. Native builds are a huge plus, as it's a lot less complicated when compiling code. It would also be a possibility to have regular CI on those platforms, which are currently not being tested at all in our CI suite. Does anyone have comments on the use of yet another CI provider? I have a PR open in anticipation of a warm response, https://github.com/scipy/scipy/pull/17029. You can see a build, and the artifacts produced at https://cirrus-ci.com/build/6727646015913984. cheers, Andrew.
On Fri, Sep 16, 2022 at 1:37 PM Andrew Nelson <andyfaff@gmail.com> wrote:
Hi all, I've been investigating the use of cirrus-ci for native building of wheels for linux_aarch64. Currently it takes about 2 hours to build a wheel on Github Actions using emulation, but on cirrus-ci it's about 5 minutes. This will enable us to fully test the wheels that are produced, rather than just a subset of tests. It would also be possible to build macosx_arm64 wheels natively rather than a cross compile. Native builds are a huge plus, as it's a lot less complicated when compiling code.
It would also be a possibility to have regular CI on those platforms, which are currently not being tested at all in our CI suite.
Does anyone have comments on the use of yet another CI provider?
+1 this will be very useful. Not having native macOS M1 and Linux aarch64 builds has been a big gap in our CI for quite some time, so it is worth the extra CI provider I'd say. The CirrusCI yaml and interface look pretty understandable too. Cheers, Ralf
I have a PR open in anticipation of a warm response, https://github.com/scipy/scipy/pull/17029. You can see a build, and the artifacts produced at https://cirrus-ci.com/build/6727646015913984.
cheers, Andrew.
_______________________________________________ SciPy-Dev mailing list -- scipy-dev@python.org To unsubscribe send an email to scipy-dev-leave@python.org https://mail.python.org/mailman3/lists/scipy-dev.python.org/ Member address: ralf.gommers@googlemail.com
NumPy is still using travis-ci for the non-x86 builds (aarch64, pp64le, s390x), but I think adding another provider is prudent since we have had problems with travis availability. Matti On Fri, Sep 16, 2022 at 6:36 AM Andrew Nelson <andyfaff@gmail.com> wrote:
Hi all, I've been investigating the use of cirrus-ci for native building of wheels for linux_aarch64. Currently it takes about 2 hours to build a wheel on Github Actions using emulation, but on cirrus-ci it's about 5 minutes. This will enable us to fully test the wheels that are produced, rather than just a subset of tests. It would also be possible to build macosx_arm64 wheels natively rather than a cross compile. Native builds are a huge plus, as it's a lot less complicated when compiling code.
It would also be a possibility to have regular CI on those platforms, which are currently not being tested at all in our CI suite.
Does anyone have comments on the use of yet another CI provider?
I have a PR open in anticipation of a warm response, https://github.com/scipy/scipy/pull/17029. You can see a build, and the artifacts produced at https://cirrus-ci.com/build/6727646015913984.
cheers, Andrew.
_______________________________________________ SciPy-Dev mailing list -- scipy-dev@python.org To unsubscribe send an email to scipy-dev-leave@python.org https://mail.python.org/mailman3/lists/scipy-dev.python.org/ Member address: matti.picus@gmail.com
participants (3)
-
Andrew Nelson -
matti picus -
Ralf Gommers