[issue31355] Remove Travis CI job: rely on buildbots

STINNER Victor added the comment: New changeset 501b324d3a940d26e0021a38aae8d896a30fbcff by Victor Stinner in branch 'master': bpo-31355: Travis CI: remove the macOS job (#3367) https://github.com/python/cpython/commit/501b324d3a940d26e0021a38aae8d896a30fbcff --

[issue31355] Remove Travis CI job: rely on buildbots

Zachary Ware added the comment: I will note that my on-going research on rewriting the buildbot config makes it look like we should be able to securely enable building PRs by checking for the 'awaiting merge' label. -- ___ Python tracker

[issue31355] Remove Travis CI job: rely on buildbots

Ned Deily added the comment: Since Travis CI time is a bottleneck for the ongoing sprint, I agree that it makes sense to disable the macOS build checks for now. Longer term, it would be nice to resolve the problem but we certainly could rely on our own macOS buildbots; I'm not aware of many

[issue31355] Remove Travis CI job: rely on buildbots

STINNER Victor added the comment: Failures of the two Allowed Failure jobs, coverage and macOS, are not reported to GitHub PR. For example, the coverage job is failing on Python 3.6 since May 2016 at least, and nobody noticed. I don't think that it's worth it to waste Travis CI resources if

[issue31355] Remove Travis CI job: rely on buildbots

Changes by STINNER Victor : -- pull_requests: +3377 ___ Python tracker ___ ___

[issue31355] Remove Travis CI job: rely on buildbots

New submission from STINNER Victor: Currently, Travis CI has a job running tests on macOS. Sadly, there is a bug on Travis: *sometimes*, the macOS job blocks a Pull Request to be merged even if macOS is marked as "Allowed Failure". If you cancel the job, it's even worse: Travis CI is marked a