[Matplotlib-devel] CI: only run macosx on travis cron jobs / only branches

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

[Matplotlib-devel] CI: only run macosx on travis cron jobs / only branches

tcaswell
Folks,


Due to the travis OSX infrastructure not being able to keep up with demand they are going to limit concurrency of jobs that us osx.

We have not seen many (any?) mac specific issues which I think means we are not getting much value out of running all of the PRs on OSX.

We can probably get better linux concurrency (and help lighten the load on travis) if we do test on OSX less.

Thoughts?

Tom

_______________________________________________
Matplotlib-devel mailing list
[hidden email]
https://mail.python.org/mailman/listinfo/matplotlib-devel
Reply | Threaded
Open this post in threaded view
|

Re: CI: only run macosx on travis cron jobs / only branches

dstansby

"If you are using Linux only on .org, you will still have access to all five concurrent builds, but if you are running both, only two of the five concurrent builds can be used for macOS at any one time."

It sounds like they're only limiting concurrent macOS builds, so in theory since we only have 1 we won't be affected. (I may have read the post wrong?). If macOS jobs build up I presume that blocks other builds from starting though?

I'm neutral either way - just testing in branches sounds like a reasonable compromise if we'll be affected by this.

David

On 26 Sep 2017 6:22 pm, "Thomas Caswell" <[hidden email]> wrote:
Folks,


Due to the travis OSX infrastructure not being able to keep up with demand they are going to limit concurrency of jobs that us osx.

We have not seen many (any?) mac specific issues which I think means we are not getting much value out of running all of the PRs on OSX.

We can probably get better linux concurrency (and help lighten the load on travis) if we do test on OSX less.

Thoughts?

Tom

_______________________________________________
Matplotlib-devel mailing list
[hidden email]
https://mail.python.org/mailman/listinfo/matplotlib-devel


_______________________________________________
Matplotlib-devel mailing list
[hidden email]
https://mail.python.org/mailman/listinfo/matplotlib-devel
Reply | Threaded
Open this post in threaded view
|

Re: CI: only run macosx on travis cron jobs / only branches

Eric Firing
In reply to this post by tcaswell
On 2017/09/26 7:22 AM, Thomas Caswell wrote:

> Folks,
>
> https://blog.travis-ci.com/2017-09-22-macos-update
>
> Due to the travis OSX infrastructure not being able to keep up with
> demand they are going to limit concurrency of jobs that us osx.
>
> We have not seen many (any?) mac specific issues which I think means we
> are not getting much value out of running all of the PRs on OSX.
>
> We can probably get better linux concurrency (and help lighten the load
> on travis) if we do test on OSX less.
>
> Thoughts?
>
> Tom

I agree with the suggestion to reduce OSX testing.

Eric
_______________________________________________
Matplotlib-devel mailing list
[hidden email]
https://mail.python.org/mailman/listinfo/matplotlib-devel
Reply | Threaded
Open this post in threaded view
|

Re: CI: only run macosx on travis cron jobs / only branches

Jouni K. Seppänen
Eric Firing <[hidden email]> writes:

> On 2017/09/26 7:22 AM, Thomas Caswell wrote:
>> Folks,
>>
>> https://blog.travis-ci.com/2017-09-22-macos-update
>>
>> Due to the travis OSX infrastructure not being able to keep up with
>> demand they are going to limit concurrency of jobs that us osx.

It's been pretty bad recently. Here's one incident:

https://www.traviscistatus.com/incidents/mc9x2wmpnvhg

That one is supposedly resolved, but it's going to take time for Travis
to work through the backlog.

One idea could be to separate the macosx backend into a different
repository and only run mac builds on that one.


Another idea: CircleCI offers the "Seed plan" for Mac OS open source
projects, but we'd need to contact them to request it:

https://circleci.com/pricing/#faq-section-os-x

That plan includes 500 minutes per month, which isn't very much, but
perhaps we could forgo builds of every revision and just trigger a build
every day or every two days, depending on how long the build would take.

--
Jouni K. Seppänen
http://www.iki.fi/jks

_______________________________________________
Matplotlib-devel mailing list
[hidden email]
https://mail.python.org/mailman/listinfo/matplotlib-devel