CI job is choking on new NumPy memory allocator warnings

Example: https://github.com/scipy/scipy/runs/4005856905?check_suite_focus=true

There’s lots of this:

scipy/interpolate/tests/test_rbf.py ..........                           [ 17%]
Exception ignored in: 'array_dealloc'
Traceback (most recent call last):
  File "/home/runner/.local/lib/python3.10/site-packages/_pytest/unraisableexception.py", line 59, in __exit__
    del self.unraisable
RuntimeWarning: Trying to dealloc data, but a memory policy is not set. If you take ownership of the data, you must also set a memory policy.

This looks like it’s in Pythran code, but nothing changed there - it seems to be due to the new memory allocator in NumPy main. @mattip can you have a look at this?

[charris]

I believe the cron jobs don’t run if a build was run in the previous 24 hours, which can be the result of a merge or a deliberate trigger.

[rgommers]

Hmm odd. Yes you are right, thanks @seberg. It looks like the NumPy nightlies arrive inconsistently, the last 3 uploads were 2, 4 and 9 days ago: https://anaconda.org/scipy-wheels-nightly/numpy/files