Add aarch64 wheels

[mattsplats]

Working build: https://travis-ci.com/github/mattsplats/h5py-wheels/builds/188922579

Related: #11

Notes:

• multibuild was updated for proper aarch64 support
• numpy <1.19 does not contain an aarch64 wheels, could potentially update this to speed things up

[mattsplats]

Looks like the repo needs to be migrated from travis-ci.org to travis-ci.com: https://docs.travis-ci.com/user/migrate/open-source-repository-migration

[mattip]

Does the build pass if you use the regular travis arm64 machines?

[mattsplats]

Unfortunately, no: https://travis-ci.org/github/MacPython/h5py-wheels/builds/735063598

No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.
Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#build-times-out-because-no-output-was-received
The build has been terminated

[mattsplats]

@mattip You could try changing the no-output timeout and re-running it.

[odidev]

@mattsplats , I pulled your changes and ran travis locally, the build was running successfully. Although it was taking around 30-35 minutes, the reason behind this is that it is taking time to build numpy as we are using older versions. numpy wheels for aarch64 are present from 1.19.0 version on wards.

Following actions can be taken here:

1. The issue looks to be sporadic, you can try to re trigger the build.
2. Update the numpy version which will help to reduce the travis build time.

[mattsplats]

Thanks @mattip - I updated numpy versions just for aarch64 for now. Let's see how this run goes.

Wasn't sure if there was a reason the older versions were being used, not having the wheel hasn't been an issue on the Graviton instances since it only takes ~5-10 minutes to compile.

[mattsplats]

Still timing out on No output has been received in the last 10m0s, even with Netty 1.19.2. Different config for your local run?

Is there a blocker for migrating from travis-ci.org to travis-ci.com?

[mattip]

Is there a blocker for migrating from travis-ci.org to travis-ci.com?

I could do it as an admin of MacPython, if the maintainers of this repo agree.

[odidev]

@matthew-brett, @tacaswell could you please let us know your interest on migrating from travis-ci.org to travis-ci.com?

[mattip]

Close/reopen to sue use travis-ci.com

Edit: typo

[mattsplats]

@mattip Thanks! Seems to be working now. I added a commit for Python 3.9 wheels as well.

[AGSaidi]

@mattip any other changes you'd like to see for this PR? It would be great to have h5py wheels.

[mattip]

I am not sure who the actual maintainers are of this repo. I see @matthew-brett, @tacaswell and @ngoldbaum have merged PRs in the past, so perhaps they could take a look at this

[tacaswell]

I can merge this, but we have moved away from using this to build the wheels to cibuildwheel on GH actions.

I have also lost track of where this will upload wheels too once they are built.

attn @takluyver who is the release manager for the recent releases.

[takluyver]

The advantage of having wheels built by our regular CI is that we know the process of building wheels is working before we actually do a release, so we're unlikely to need a last minute scramble to update the build infrastructure.

On the other hand, we've already got a lot of CI machinery (testing with various Python, HDF5 and NumPy versions, plus different platforms), and I don't particularly want to make that even heavier with more architectures. So maybe having the x64 wheels built in the project and other architectures here is a decent compromise.

Where do the wheels from this go? The README points to http://wheels.scipy.org/ and https://3f23b170c54c2533c070-1c8a9b3114517dc5fe17b7c3f8c63a43.ssl.cf2.rackcdn.com/ , but both of those give me errors.

[mattip]

The upload url on rackcdn has been dead for a while, it was mirrored as http://wheels.scipy.org.

If your regular CI is using cibuildwheel, then I think moving only the non-x86 builds to use cibuildwheel on travis would by your best bet. Instructions to do that are here.

[W]e have moved away from using this to build the wheels to cibuildwheel on GH actions

I looked around a bit on https://github.com/h5py/h5py for github actions, but found only an azure pipelines CI job. Is that what you meant? In any case, the artifact upload will need to be added to the typical cibuildwheel travis skeleton I linked to above.

[tacaswell]

Is that what you meant? In any case, the artifact upload will need to be added to the typical cibuildwheel travis skeleton I linked to above.

Yes, sorry I I was confused about where we landed 🐑 . The important point is we are not relying on this repo any longer for the x86 wheels.