Rebuild for pypy

[regro-cf-autotick-bot]

This PR has been triggered in an effort to update pypy.

Notes and instructions for merging this PR:

1. Please merge the PR only after the tests have passed.
2. Feel free to push to the bot's branch to update this PR if needed.

Please note that if you close this PR we presume that the feedstock has been rebuilt, so if you are going to perform the rebuild yourself don't close this PR until the your rebuild has been merged.

This package has the following downstream children:
adaptive-scheduler
airflow
allensdk
alpenglow
bcolz
And potentially more.

If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

_{This PR was created by the cf-regro-autotick-bot.
The cf-regro-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. If you would like a local version of this bot, you might consider using rever. Rever is a tool for automating software releases and forms the backbone of the bot's conda-forge PRing capability. Rever is both conda (conda install -c conda-forge rever) and pip (pip install re-ver) installable.
Finally, feel free to drop us a line if there are any issues!
This PR was generated by https://circleci.com/gh/regro/circle_worker/15048, please use this URL for debugging}

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.

Here's what I've got...

For recipe:

• Failed to even lint the recipe, probably because of a conda-smithy bug 😢. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint . from the recipe directory.

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipe:

• License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

[h-vetinari]

@conda-forge-admin, please restart ci

[h-vetinari]

@conda-forge-admin, please rerender

[h-vetinari]

Seems the problem was that the pypy build was looking for a numpy version that hadn't been built for pypy, but the rerender solved that problem. :)

[h-vetinari]

All the travis builds on Aarch stalled hard. Maybe someone should manually kick them to restart (I don't have the rights).

[TomAugspurger]

I'm not sure if the Aarch builds have ever completed.

…

On Thu, Apr 16, 2020 at 7:31 AM h-vetinari ***@***.***> wrote: All the travis builds on Aarch stalled hard. Maybe someone should manually kick them to restart (I don't have the rights). — You are receiving this because your review was requested. Reply to this email directly, view it on GitHub <#78 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKAOIXAFYOSB6CB3BSBWZ3RM33ALANCNFSM4LHEGBWA> .

[h-vetinari]

@TomAugspurger: I'm not sure if the Aarch builds have ever completed.

Interestingly, while the last run (for 1.0.3) errored, the builds nevertheless succeeded somehow and are seeing downloads.

[h-vetinari]

@h-vetinari: Interestingly, while the last run (for 1.0.3) errored, the builds nevertheless succeeded somehow and are seeing downloads.

Actually, that's possibly a pretty serious issue (CI seemingly stalled, yet packages getting uploaded) that's happened at least for the last two pandas (patch) releases. CC @conda-forge/core

[xhochy]

ppc64le is still at v0.25.3, so there were no spurious uploads happening. Note that aarch64 builds run on drone.io, travis only builds ppc64le.

[xhochy]

@conda-forge-admin please rerender

[h-vetinari]

@xhochy: ppc64le is still at v0.25.3, so there were no spurious uploads happening. Note that aarch64 builds run on drone.io, travis only builds ppc64le.

Right, sorry for getting my wires crossed on that 😅

[h-vetinari]

Right, so it seems the ppc64le builds are extremely slow (~2h for cpython, 2:50h for pypy), but they succeed on azure!

Maybe they wouldn't even be timing out on travis if they were left to run, rather than killed after 10 min with no output (but even then, travis wouldn't be an alternative because the build times are much longer than their default timeout of 50/60 min).

[xhochy]

Travis should be able to build them faster as Azure is virtualized and Travis would run natively on ppc64le.

[isuruf]

azure is running under qemu which was like 6x slower for the numpy build.

[xhochy]

@conda-forge/pandas This is ready for review. I moved the ppc64le build to Azure to get it passing bu t it now takes very long. Moving it back to Travis would improve the times again but sadly the build stalls after 10min.

[TomAugspurger]

I suspect none of the pandas maintainers have experience with pypy or power. I'm happy to defer to the CF experts here.