On Sep 19, 2017, at 15:32, Victor Stinner <victor.stin...@gmail.com> wrote: > > 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.)
If the macOS tests aren’t stable, then yes, removing them is better than frustrating developers who can’t reproduce CI failures, even on the CI machines let alone their own development boxes. I forget though, was it a problem with macOS CI stability or general throughput? I thought they just couldn’t keep up with the workload, in which case it seems like we should be able to throw more resources at it, right? -Barry
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
