[Numpy-discussion] Re: MacPython travis funds have run out (again)

2022-01-14 Thread Matti Picus 



On 14/1/22 3:04 am, Charles R Harris wrote:

Hi All,

Travis wheel build problems again. There is still a positive balance, 
but apparently it is insufficiently positive. Which is strange if 
ARM64 is free. Wheel builds have been failing since last weekend.


Matti, could you ask for more credits? I'm thinking we really need to 
move off travis for ARM builds.


Chuck



I sent a request to supp...@travis-ci.com.


If we want to move off travis for aarch64, I think the only option right 
now is to use emulation, conda-forge does this on Azure machines [0] and 
the build + tests takes ~40 minutes. I can only imagine how long it 
would take to do move SciPy to a QEMU.



Do we have a way to reach out to an industry contact in the ARM 
foundation or to AWS (who have aarch 64 cloud machines) or NVidia (who 
also manufacture aarch64 machines) and discuss the problem with them?


Matti


[0] 
https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=434709&view=logs&jobId=e9afaa34-1a0f-534e-78fc-fae528ccd915&j=e9afaa34-1a0f-534e-78fc-fae528ccd915&t=48395e60-bc5f-5e45-7455-d404f0c95f3a


___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to numpy-discussion-le...@python.org
https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
Member address: arch...@mail-archive.com

[Numpy-discussion] Re: MacPython travis funds have run out (again)

2022-01-14 Thread Kevin Sheppard 
As a data point against relying on QEMU: statsmodels times out (5+ hours)
when trying to build with QEMU rising cibuildwheel and GitHub actions.

Kevin


On Fri, Jan 14, 2022, 08:53 Matti Picus  wrote:

>
> On 14/1/22 3:04 am, Charles R Harris wrote:
> > Hi All,
> >
> > Travis wheel build problems again. There is still a positive balance,
> > but apparently it is insufficiently positive. Which is strange if
> > ARM64 is free. Wheel builds have been failing since last weekend.
> >
> > Matti, could you ask for more credits? I'm thinking we really need to
> > move off travis for ARM builds.
> >
> > Chuck
> >
>
> I sent a request to supp...@travis-ci.com.
>
>
> If we want to move off travis for aarch64, I think the only option right
> now is to use emulation, conda-forge does this on Azure machines [0] and
> the build + tests takes ~40 minutes. I can only imagine how long it
> would take to do move SciPy to a QEMU.
>
>
> Do we have a way to reach out to an industry contact in the ARM
> foundation or to AWS (who have aarch 64 cloud machines) or NVidia (who
> also manufacture aarch64 machines) and discuss the problem with them?
>
> Matti
>
>
> [0]
>
> https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=434709&view=logs&jobId=e9afaa34-1a0f-534e-78fc-fae528ccd915&j=e9afaa34-1a0f-534e-78fc-fae528ccd915&t=48395e60-bc5f-5e45-7455-d404f0c95f3a
>
> ___
> NumPy-Discussion mailing list -- numpy-discussion@python.org
> To unsubscribe send an email to numpy-discussion-le...@python.org
> https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
> Member address: kevin.k.shepp...@gmail.com
>
___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to numpy-discussion-le...@python.org
https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
Member address: arch...@mail-archive.com

[Numpy-discussion] Re: MacPython travis funds have run out (again)

2022-01-14 Thread Matti Picus 




On Fri, Jan 14, 2022, 08:53 Matti Picus > wrote:



...
If we want to move off travis for aarch64, I think the only option
right
now is to use emulation, conda-forge does this on Azure machines
[0] and
the build + tests takes ~40 minutes. I can only imagine how long it
would take to do move SciPy to a QEMU.


...
Matti


[0]

https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=434709&view=logs&jobId=e9afaa34-1a0f-534e-78fc-fae528ccd915&j=e9afaa34-1a0f-534e-78fc-fae528ccd915&t=48395e60-bc5f-5e45-7455-d404f0c95f3a



On 14/1/22 12:08 pm, Kevin Sheppard wrote:
As a data point against relying on QEMU: statsmodels times out (5+ 
hours) when trying to build with QEMU rising cibuildwheel and GitHub 
actions.


Kevin



Interesting. It seems to work on the azure builds from conda-forge, I 
wonder what is different. Are the time out build logs still around?


Matti


[1] https://github.com/conda-forge/statsmodels-feedstock/runs/4196021348

___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to numpy-discussion-le...@python.org
https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
Member address: arch...@mail-archive.com

[Numpy-discussion] Re: MacPython travis funds have run out (again)

2022-01-14 Thread Kevin Sheppard 
Thanks for asking, and prompting me to take a look – it turns out the aarch64 built fine: cp310-manylinux_aarch64 finished in 2784.95s What times out was: Building cp310-musllinux_aarch64 wheel Which would have needed to build NumPy, then SciPy, Cython, then Statsmodels.   Now we can have aarch64 wheel one I block musllinux_aarch64. Kevin  From: Matti PicusSent: Friday, January 14, 2022 10:31 AMTo: numpy-discussion@python.orgSubject: [Numpy-discussion] Re: MacPython travis funds have run out (again)   > On Fri, Jan 14, 2022, 08:53 Matti Picus > > wrote:> > > ...> If we want to move off travis for aarch64, I think the only option> right> now is to use emulation, conda-forge does this on Azure machines> [0] and> the build + tests takes ~40 minutes. I can only imagine how long it> would take to do move SciPy to a QEMU.> > > ...> Matti> > > [0]> https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=434709&view=logs&jobId=e9afaa34-1a0f-534e-78fc-fae528ccd915&j=e9afaa34-1a0f-534e-78fc-fae528ccd915&t=48395e60-bc5f-5e45-7455-d404f0c95f3a> > > On 14/1/22 12:08 pm, Kevin Sheppard wrote:>> As a data point against relying on QEMU: statsmodels times out (5+ >> hours) when trying to build with QEMU rising cibuildwheel and GitHub >> actions.>> >> Kevin  Interesting. It seems to work on the azure builds from conda-forge, I wonder what is different. Are the time out build logs still around? Matti  [1] https://github.com/conda-forge/statsmodels-feedstock/runs/4196021348 ___NumPy-Discussion mailing list -- numpy-discussion@python.orgTo unsubscribe send an email to numpy-discussion-le...@python.orghttps://mail.python.org/mailman3/lists/numpy-discussion.python.org/Member address: kevin.k.shepp...@gmail.com 
___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to numpy-discussion-le...@python.org
https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
Member address: arch...@mail-archive.com

[Numpy-discussion] Re: MacPython travis funds have run out (again)

2022-01-14 Thread Matti Picus 



On 14/1/22 10:51 am, Matti Picus wrote:


On 14/1/22 3:04 am, Charles R Harris wrote:

Hi All,

Travis wheel build problems again. There is still a positive balance, 
but apparently it is insufficiently positive. Which is strange if 
ARM64 is free. Wheel builds have been failing since last weekend.


Matti, could you ask for more credits? I'm thinking we really need to 
move off travis for ARM builds.


Chuck



I sent a request to supp...@travis-ci.com.


If we want to move off travis for aarch64, I think the only option 
right now is to use emulation, conda-forge does this on Azure machines 
[0] and the build + tests takes ~40 minutes. I can only imagine how 
long it would take to do move SciPy to a QEMU.



Do we have a way to reach out to an industry contact in the ARM 
foundation or to AWS (who have aarch 64 cloud machines) or NVidia (who 
also manufacture aarch64 machines) and discuss the problem with them?


Matti


[0] 
https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=434709&view=logs&jobId=e9afaa34-1a0f-534e-78fc-fae528ccd915&j=e9afaa34-1a0f-534e-78fc-fae528ccd915&t=48395e60-bc5f-5e45-7455-d404f0c95f3a




The builds are running again [1].

Matti


[1] https://app.travis-ci.com/github/MacPython/numpy-wheels

___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to numpy-discussion-le...@python.org
https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
Member address: arch...@mail-archive.com

[Numpy-discussion] Re: MacPython travis funds have run out (again)

2022-01-14 Thread Charles R Harris 
On Fri, Jan 14, 2022 at 7:21 AM Matti Picus  wrote:

>
> On 14/1/22 10:51 am, Matti Picus wrote:
> >
> > On 14/1/22 3:04 am, Charles R Harris wrote:
> >> Hi All,
> >>
> >> Travis wheel build problems again. There is still a positive balance,
> >> but apparently it is insufficiently positive. Which is strange if
> >> ARM64 is free. Wheel builds have been failing since last weekend.
> >>
> >> Matti, could you ask for more credits? I'm thinking we really need to
> >> move off travis for ARM builds.
> >>
> >> Chuck
> >>
> >
> > I sent a request to supp...@travis-ci.com.
> >
> >
> > If we want to move off travis for aarch64, I think the only option
> > right now is to use emulation, conda-forge does this on Azure machines
> > [0] and the build + tests takes ~40 minutes. I can only imagine how
> > long it would take to do move SciPy to a QEMU.
> >
> >
> > Do we have a way to reach out to an industry contact in the ARM
> > foundation or to AWS (who have aarch 64 cloud machines) or NVidia (who
> > also manufacture aarch64 machines) and discuss the problem with them?
> >
> > Matti
> >
> >
> > [0]
> >
> https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=434709&view=logs&jobId=e9afaa34-1a0f-534e-78fc-fae528ccd915&j=e9afaa34-1a0f-534e-78fc-fae528ccd915&t=48395e60-bc5f-5e45-7455-d404f0c95f3a
> >
>
> The builds are running again [1].
>
> Matti
>
>
> [1] https://app.travis-ci.com/github/MacPython/numpy-wheels
>
>
Thanks Matti.

Chuck
___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to numpy-discussion-le...@python.org
https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
Member address: arch...@mail-archive.com

[Numpy-discussion] NumPy 1.22.1 has been released.

2022-01-14 Thread Charles R Harris 
Hi All,

On behalf of the NumPy team, I'm pleased to announce the release of NumPy
1.22.1. NumPy 1.22.1 fixes several bugs discovered after the 1.22.0
release. Notable fixes are:

   - Fix for f2PY docstring problems (SciPy)
   - Fix for reduction type problems (AstroPy)
   - Fixes for various typing bugs.

The Python versions supported in this release are 3.8-3.10.  Wheels can be
downloaded from PyPI ; source
archives, release notes, and wheel hashes are available on Github
. Linux users will
need pip >= 0.19.3 in order to install the manylinux2014 wheels. A recent
version of pip is needed to install the universal2 macos wheels.

*Contributors*

A total of 14 people contributed to this release.  People with a "+" by
their
names contributed a patch for the first time.

   - Arryan Singh
   - Bas van Beek
   - Charles Harris
   - Denis Laxalde
   - Isuru Fernando
   - Kevin Sheppard
   - Matthew Barber
   - Matti Picus
   - Melissa Weber Mendonça
   - Mukulika Pahari
   - Omid Rajaei +
   - Pearu Peterson
   - Ralf Gommers
   - Sebastian Berg


*Pull requests merged*
A total of 20 pull requests were merged for this release.

   - #20702: MAINT, DOC: Post 1.22.0 release fixes.
   - #20703: DOC, BUG: Use pngs instead of svgs.
   - #20704: DOC: Fixed the link on user-guide landing page
   - #20714: BUG: Restore vc141 support
   - #20724: BUG: Fix array dimensions solver for multidimensional
   arguments...
   - #20725: TYP: change type annotation for ``__array_namespace__`` to
   ModuleType
   - #20726: TYP, MAINT: Allow ``ndindex`` to accept integer tuples
   - #20757: BUG: Relax dtype identity check in reductions
   - #20763: TYP: Allow time manipulation functions to accept ``date`` and
   ``timedelta``...
   - #20768: TYP: Relax the type of ``ndarray.__array_finalize__``
   - #20795: MAINT: Raise RuntimeError if setuptools version is too recent.
   - #20796: BUG, DOC: Fixes SciPy docs build warnings
   - #20797: DOC: fix OpenBLAS version in release note
   - #20798: PERF: Optimize array check for bounded 0,1 values
   - #20805: BUG: Fix that reduce-likes honor out always (and live in the...
   - #20806: BUG: ``array_api.argsort(descending=True)`` respects
   relative...
   - #20807: BUG: Allow integer inputs for pow-related functions in
   ``array_api``
   - #20814: DOC: Refer to NumPy, not pandas, in main page
   - #20815: DOC: Update Copyright to 2022 [License]
   - #20819: BUG: Return correctly shaped inverse indices in array_api
   set...

Cheers,

Charles Harris
___
NumPy-Discussion mailing list -- numpy-discussion@python.org
To unsubscribe send an email to numpy-discussion-le...@python.org
https://mail.python.org/mailman3/lists/numpy-discussion.python.org/
Member address: arch...@mail-archive.com