@mattip @rgommers I think this is ready for an initial review now.

There's still somethings that I have to add(e.g. wheel uploading, and the triggering mechanism present on GHA), but it basically works now. It should be trivial to add, as it would probably just mean refactoring out the bash logic in GHA to a shared file under tools and calling it from both Travis CI and GHA.

For wheel uploading, someone needs to add the upload tokens to both staging and nightly under the names NUMPY_STAGING_UPLOAD_TOKEN and NUMPY_NIGHTLY_UPLOAD_TOKEN for Travis CI.

Isn't this running the build/test twice: once in CIBUILDWHEEL and once in the travis scripts at the end?

No, I'm pretty sure I overrided the build/test components on the wheel builders.

(Because I didn't override the before_install step, it still executes on the wheel builders. Should be harmeless given that building happens in a docker container, but will try to fix in next commit.)

When I look at the travis-ci run for this PR I see 7 jobs. It is not clear from the ENV which architecture it is, but here is a table. Can you somehow disable runs 3 and 4?

Oh, I think I see what you mean now.
Is the idea to move the testing on aarch64 from the standalone job to inside the test phase of the cibuildwheel build?

Is the idea to move the testing on aarch64 from the standalone job to inside the test phase of the cibuildwheel build?

Either that or put an if not wheels so that we either build wheels or run the old build scripts

I think so.

Edit: rephrasing to simply agree

Do you want to set up the upload tokens now or leave that for a follow up? I forgot to mention this, but someone also has to set up a cron job too, through the Travis UI to run the weekly builds.

(Mostly likely this PR will break the uploading process again for wheels so it might require some tuning but I can't tell until its been merged. Its still likely a good first step as the wheels build successfully)

Did you try /tools/wheels/upload_wheels.sh on your branch?

I wonder why it is echoing the command here

Do you want to set up the upload tokens now or leave that for a follow up?

Done, added NUMPY_NIGHTLY_UPLOAD_TOKEN and NUMPY_STAGING_UPLOAD_TOKEN. These should be available as ${NUMPY_NIGHTLY_UPLOAD_TOKEN} and ${NUMPY_STAGING_UPLOAD_TOKEN}

I forgot to mention this, but someone also has to set up a cron job too, through the Travis UI to run the weekly builds.

Done.

Did you try /tools/wheels/upload_wheels.sh on your branch?

I wonder why it is echoing the command here

I think it is working, just a little hard to see due to the size of the log.

Thanks @lithomas1.

I manually triggered a build https://app.travis-ci.com/github/numpy/numpy/builds/246680087 by going to the "More Options" pulldown. Hopefully only availalbe to maintainers :). Let's see what happens

A manual trigger has the line TRAVIS_EVENT_TYPE is api but there is no condition for that in the script, so it does not upload. I think we should add one.

Now the manual trigger does something, but the upload cannot find the wheel

ls: cannot access './wheelhouse/*.whl': No such file or directory

Wheels for aarch64 are uploading! https://anaconda.org/scipy-wheels-nightly/numpy/files

Nice. Thanks a bunch for fixing the typos I made.