BLD/CI: re-enable ILP64 usage and PyPy job in Azure#24238
Conversation
Also improve the `show_config` output (fixes one of the issues discussed in numpygh-24200), and improve handling of BLAS related logic in `numpy/meson.build`. The `OPENBLAS64_` environment variable is only used in `numpy.distutils.system_info`, so remove it from the places where we no longer use `numpy.distutils`.
|
Not a bad start, the only failure is the re-enabled PyPy job, with: EDIT: the numpy build seems to be fine, result is |
4aa5c85 to
9654944
Compare
This was broken with `undefined symbol: dlapy3_` because the test suite imports `linalg.lapack_lite` directly. See numpygh-24200 for more details.
`threadpoolctl.threadpool_info()` returns an empty list for some reason, even though all tests on PyPy pass. This works locally just fine too with PyPy 7.3.11
9654944 to
f10e6b7
Compare
|
This should be good to go now. @charris I think the |
mattip
left a comment
There was a problem hiding this comment.
Just one small niggle, overall a nice cleanup. It is fine to merge as-is.
| if len(data) != 1: | ||
| if platform.python_implementation() == 'PyPy': | ||
| print(f"Check broken in CI on PyPy, data is: {data}") | ||
| return |
There was a problem hiding this comment.
Maybe not worth the effort to explore, but this is strange.
There was a problem hiding this comment.
It failed in CI, then I did go through the effort of setting up a PyPy dev env locally, but there it worked fine. So I'd like to punt on this at least for now.
|
Thanks @rgommers |
Also improve the
show_configoutput (fixes one of the issues discussed in gh-24200), and improve handling of BLAS related logic innumpy/meson.build.The
OPENBLAS64_environment variable is only used innumpy.distutils.system_info, so remove it from the places where we no longer usenumpy.distutils.