[python-committers] Travis CI: macOS is now blocking -- remove macOS from Travis CI?

[Victor Stinner]

Hi,

The macOS job has been removed from Travis CI at the beginnig of the
CPython sprint two weeks ago. Since the macOS build was removed, I'm
less annoyed by Travis CI: it seems more stable.

Are you ok to not add again the macOS job to Travis CI?

Again, my rationale is that we already have 3 macOS buildbots and I'm
looking closely at all buildbot failures. I try to keep track of *all*
failures, even random failure. A recent macOS example:
https://bugs.python.org/issue31510

Sadly, remaining random failures are the most rare and most difficult
to reproduce. (I fixed a lot of them last months.)

Victor

2017-09-06 1:30 GMT+02:00 Victor Stinner <victor.stinner at gmail.com>:
> Hi,
>
> I was bitten again by the issue on https://github.com/python/cpython/pull/3350
>
> After restarting the Travis CI build twice (first by me, then by
> Zach), I was able to merge it. But it's painful to have to restart a
> whole build. And it wastes Travis CI resources :-(
>
> So I just proposed to drop the macOS job: https://bugs.python.org/issue31355
>
> Please read the issue for the full rationale.
>
> Victor
>
> 2017-09-01 19:15 GMT+02:00 Victor Stinner <victor.stinner at gmail.com>:
>> Hi,
>>
>> Since today, it seems like the macOS task of a Travis CI job to
>> validate a pull request hangs the whole job.
>>
>> Don't try to cancel the macOS job, or the whole job will be marked as
>> failed! ... even if macOS is in the "Allowed Failure" section. I don't
>> know the best way to "repair" such job. I use "restart job" which
>> restarts all tasks, even the completed *and successful* Linux and doc
>> jobs.
>>
>> I have PRs waiting for longer than 2 hours for Travis CI. The macOS
>> job is seen as "queued".
>>
>> Yesterday, it was possible to merge a PR even if the macOS job was
>> still queued (no started).
>>
>> I never wait for macOS, since, as I wrote, it can take longer than 1
>> hour. Moreover, macOS failures are not reported to the GitHub UI :-(
>> (Hum, in fact, I'm not sure about that.)
>>
>> Maybe we should remove the pre-commit macOS task from the Travis CI
>> config to focus on post-commit macOS buildbots? If we remove it,
>> should we remove it from 2.7, 3.6 and master branches?
>>
>> We have 3 macOS buildbots:
>>
>> * x86 Tiger 3.x
>> * x86-64 El Capitan 3.x
>> * x86-64 Sierra 3.x
>>
>> All three are currently green ;-)
>>
>> In the last 3 months, the macOS task of Travis CI caused multiple issues :-/
>>
>> Victor