Re: CI: only run macosx on travis cron jobs / only branches
"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.
> 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.
I agree with the suggestion to reduce OSX testing.
> On 2017/09/26 7:22 AM, Thomas Caswell wrote:
>> 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:
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.