[python-committers] macOS Travis CI job became mandatory? (original) (raw)
Victor Stinner victor.stinner at gmail.com
Mon Jun 26 11:22:24 EDT 2017
- Previous message (by thread): [python-committers] macOS Travis CI job became mandatory?
- Next message (by thread): [python-committers] macOS Travis CI job became mandatory?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
End of the funny story: the macOS job was killed by Travis CI: "The job exceeded the maximum time limit for jobs, and has been terminated."
Thanks to that, the whole Travis CI job on the PR became green...
I would suggest to remove the pre-commit macOS job. We have enough macOS post-commit jobs on buildbots, no?
Victor
2017-06-26 16:46 GMT+02:00 Victor Stinner <victor.stinner at gmail.com>:
48 minutes later: the macOS is running for 33 minutes, but Travis CI fails to retrieve the logs :-/ https://travis-ci.org/python/cpython/jobs/247090627
Victor 2017-06-26 15:57 GMT+02:00 Victor Stinner <victor.stinner at gmail.com>: Hi,
I was waiting for the result of Travis CI: 3 jobs already completed, but the macOS job was still running. The macOS job is marked as "allowed failure". I cancelled the job, but then the Travis CI was marked as failed in the PR :-/ So I restarted the job. Is it normal to have to wait for the slow macOS job to be able to merge a PR? It's a recent change, no? Victor
- Previous message (by thread): [python-committers] macOS Travis CI job became mandatory?
- Next message (by thread): [python-committers] macOS Travis CI job became mandatory?
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]