Add Travis-CI config to build aarch64 wheels

[janaknat]

Travis-CI allows for the creation of aarch64 wheels.

Graviton2 instances can be used to build aarch64 artifacts by using the following tag:

arch: arm64-graviton2
dist: focal
virt: vm
group: edge

[janaknat]

This will require the tests be run in travis-ci.com instead of travis-ci.org.

The steps to transition can be found at: https://docs.travis-ci.com/user/migrate/open-source-repository-migration
A PR for additional info on migration: travis-ci/docs-travis-ci-com#2886

Successful build log: https://travis-ci.com/github/janaknat/pandas-wheels/builds/183585039

[janaknat]

Blog post detailing Graviton2 support in Travis-CI: https://blog.travis-ci.com/2020-09-11-arm-on-aws

[TomAugspurger]

Thanks. Is NumPy building and shipping aarch64 wheels?

[janaknat]

@TomAugspurger Yes NumPy has started shipping aarch64 wheels: https://pypi.org/project/numpy/#files

[janaknat]

Any feedback on this?

[TomAugspurger]

It's on my list to look at, but I won't have a chance to look this week. Dunno if any of the other maintainers will be able to.

…

On Mon, Sep 14, 2020 at 11:31 AM Janakarajan Natarajan < ***@***.***> wrote: Any feedback on this? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#99 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKAOIVNP6D43UHYPFWDTBTSFZANDANCNFSM4RCZK4CA> .

[mattip]

NumPy is not using travis-ci.com, it is using travis-ci.org. In order to move to travis-ci.com, as I have commented elsewhere, we need a way to resolve the issue that creating a travis-ci.com login requires giving them read-write access to all your private and public github repos.

[janaknat]

@mattip @TomAugspurger Can we migrate Macpython/pandas-wheels to travis-ci.com and try with Graviton2? Similar to what was done with scipy-wheels (MacPython/scipy-wheels#93).

[mattip]

I can do the legwork to migrate the repo (under my alias @multibuilder) if the core maintainers sign off on the idea. This would mean they would now need to sign into travis-ci.com rather than travis-ci.org or ask me in order to manage the build settings: set secrets, stop/start specific builds. Automatic triggering would work as before. We recently migrated the scipy-wheel build to travis-ci.com, so this second migration should be easier.

[janaknat]

@TomAugspurger Is migration to travis-ci.com okay?

[TomAugspurger]

@mattip if you're able to do the migration under the @multibulider account, that'd be great.

[mattip]

Closing/Reopening to trigger the build on travis-ci.com

[mattip]

For future reference the steps are:

• go to MacPython/settings (for org owners) ->installed github apps -> add the repo that wishes to migrate
• go to https://travis-ci.com/organizations/MacPython/migrate (again, for org owners), the repo should appear there. Authorize the transition.
• come back to a PR, close/open to restart the build.

So you can ignore the "continuous-integration/travis-ci/pr" CI failure, since that is from the old webhook at travis-ci.org and look at the "Travis CI - Pull Request" line instead, which should take you to travis-ci.com.

[janaknat]

Thanks @mattip

[TomAugspurger]

Has this secret been uploaded? I don't see it in https://travis-ci.com/github/MacPython/pandas-wheels/settings, but I'm not sure if I should be seeing it.

[mattip]

You are correct. The secret is wrong anyway, it should be the secret(s) from anaconda.org, like the azure pipeline.

[mattip]

So someone will need to add those tokens to travis-ci.com

[TomAugspurger]

I added PANDAS_STAGING_UPLOAD_TOKEN and PANDAS_NIGHTLY_UPLOAD_TOKEN through the travis UI.

[TomAugspurger]

Alrighty, hopefully this works. Thanks for your help here Matti and @janaknat.