On 31/12/21 3:50 am, Charles R Harris wrote:

On Thu, Dec 30, 2021 at 6:26 PM Charles R Harris mailto:charlesr.harris@gmail.com> wrote:

Hi All,

We need to get more credits in order to run MacPython/numpy-wheels builds on travis. Anyone recall how to go about this?

Chuck

MacPython has used 800550 of 800000 credits.  NumPy has used 625860 of 800000 credits, so should be good for a couple of months. SciPy has one credit left, but doesn't use travis. I think the MacPython credits covers everyone who uses multibuild and travis, so NumPy is likely not the only one affected.

Chuck

I requested more OpenSource credits for MacPython. The MacPython credits cover many of the wheel-building projects, the main repos (numpy/numpy) are under different accounts. I last reqeusted credits for MacPython in October. A bit more information: Travis-ci.com bills differently for each platform. For x86, they bill 10 credits per minute on linux 20 credits per minute on windows 50 credits per minute on macos aarch64 (arm linux), ppc, and s390x are **not billed** against credits. I think this is because other companies provide the actual hardware runners. Some of the projects under MacPython like matplotlib have migrated off travis and use cibuildwheel in their main repo [0], using qemu for arm64. Others  like numpy-wheels and openblas-libs moved their x86 builds to other providers, their travis builds actually consume 0 credits. h5py-wheels, scipy-wheels, pandas-wheels and others are still consuming credits for their x86 builds. If all the projects moved to other providers it would save opening requests for more credits, admittedly it is easier to request credits than to move the build :). I could also be more proactive in tracking the credit situation and request a renewal before they run out, I will set a reminder to do so 2 1/2 months from now. Matti [0] https://github.com/matplotlib/matplotlib/blob/main/.github/workflows/cibuild...

We are back in business with 100k credits. Matti On Fri, 31 Dec 2021 at 08:43, James Tocknell wrote:

I'll need to check with the other maintainers (see https://github.com/h5py/h5py/issues/2026), but I believe h5py shouldn't need the x86 builds any more (I'm less sure about the other systems)?

James

On Fri, 31 Dec 2021 at 17:03, Matti Picus wrote:

...

On 31/12/21 3:50 am, Charles R Harris wrote:

...

On Thu, Dec 30, 2021 at 6:26 PM Charles R Harris mailto:charlesr.harris@gmail.com> wrote:

Hi All,

We need to get more credits in order to run MacPython/numpy-wheels builds on travis. Anyone recall how to go about this?

Chuck

MacPython has used 800550 of 800000 credits. NumPy has used 625860 of 800000 credits, so should be good for a couple of months. SciPy has one credit left, but doesn't use travis. I think the MacPython credits covers everyone who uses multibuild and travis, so NumPy is likely not the only one affected.

Chuck

I requested more OpenSource credits for MacPython. The MacPython credits cover many of the wheel-building projects, the main repos (numpy/numpy) are under different accounts. I last reqeusted credits for MacPython in October.

A bit more information:

Travis-ci.com bills differently for each platform.

For x86, they bill

10 credits per minute on linux

20 credits per minute on windows

50 credits per minute on macos

aarch64 (arm linux), ppc, and s390x are **not billed** against credits. I think this is because other companies provide the actual hardware

runners.

...

Some of the projects under MacPython like matplotlib have migrated off travis and use cibuildwheel in their main repo [0], using qemu for arm64.

Others like numpy-wheels and openblas-libs moved their x86 builds to other providers, their travis builds actually consume 0 credits.

h5py-wheels, scipy-wheels, pandas-wheels and others are still consuming credits for their x86 builds. If all the projects moved to other providers it would save opening requests for more credits, admittedly it is easier to request credits than to move the build :). I could also be more proactive in tracking the credit situation and request a renewal before they run out, I will set a reminder to do so 2 1/2 months from

now.

...

Matti

[0]

https://github.com/matplotlib/matplotlib/blob/main/.github/workflows/cibuild...

...

_______________________________________________ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-leave@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: aragilar+numpy@gmail.com

_______________________________________________ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-leave@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: matti.picus@gmail.com

Hello Matti, Charles, I'm a minor numpy contributor but mostly follow the mailing list with an eye on any impacts downstream for Biopython. Like numpy and scipy etc, we had been using TravisCI to build our wheels: https://github.com/biopython/biopython-wheels Lots of other projects using multibuild are in a similar situation. It looks like we will probably migrate to GitHub actions, but using TravisCI for one more release is tempting if getting credits is straight forward. Do you have any advice on how to request TravisCI credits (I'd be happy to discuss off list), or would you advise us to focus on the migration now (which pushes back any release plans). Thank you, Peter On Fri, Dec 31, 2021 at 8:36 PM Charles R Harris wrote:

On Fri, Dec 31, 2021 at 12:30 PM matti picus wrote:

...

We are back in business with 100k credits. Matti

Thanks Matti.

<snip>

Chuck

_______________________________________________ NumPy-Discussion mailing list -- numpy-discussion@python.org To unsubscribe send an email to numpy-discussion-leave@python.org https://mail.python.org/mailman3/lists/numpy-discussion.python.org/ Member address: p.j.a.cock@googlemail.com

That's great, thanks! Hopefully I'll get time to sort that out soon. Peter On Thu, Jan 6, 2022 at 3:23 PM Matti Picus wrote:

On 6/1/22 2:15 pm, Peter Cock wrote:

...

Hello Matti, Charles,

...

Do you have any advice on how to request TravisCI credits (I'd be happy to discuss off list), or would you advise us to focus on the migration now (which pushes back any release plans).

Thank you,

Peter

Here is what travis-ci wrote me when I asked about free credits for multibuild:

-----------------------

We offer an Open Source Subscription for free to non-commercial open-source projects. To qualify for an Open Source subscription, the project must meet the following requirements:

* You are a project lead or regular committer (latest commit in the last month) * Project must be at least 3 months old and is in active development (with regular commits and activity) * Project meets the OSD https://opensource.org/docs/osd specification * Project must not be an expressly commercial project * Project can not provide commercial services or distribute paid versions of the software

------------

So I wrote to support@travis-ci.com:

-------------------------------------

I am one of the project leads and the number 4 contributor to the project in 2021

https://github.com/multi-build/multibuild/graphs/contributors?from=2021-01-04&to=2021-10-13&type=c

The graph above shows that the project is under active development.

The license for the project is BSD 2

https://github.com/multi-build/multibuild/blob/devel/LICENSE

The project is a support framework for open source projects and provides no commercial services or paid versions. ---------------------------------------- Matti