macOS Travis CI job became mandatory?
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
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@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
Le 26/06/2017 à 16:46, Victor Stinner a écrit :
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
Just kill the job :-)
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@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@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
Le 26/06/2017 à 17:22, Victor Stinner a écrit :
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?
Given that it doesn't hurt to keep it, I would rather keep it. It allows to quickly test for OS X-specific issues.
Regards
Antoine.
2017-06-26 17:25 GMT+02:00 Antoine Pitrou <antoine@python.org>:
Given that it doesn't hurt to keep it, I would rather keep it. It allows to quickly test for OS X-specific issues.
According to my bad experience of today, it took longer than 1h30 to get the [Merge] button... Before, it took around 20 min.
Well, it only happed me once. Maybe macOS doesn't like Monday?
Victor
On Mon, 26 Jun 2017 at 09:22 Victor Stinner <victor.stinner@gmail.com> wrote:
2017-06-26 17:25 GMT+02:00 Antoine Pitrou <antoine@python.org>:
Given that it doesn't hurt to keep it, I would rather keep it. It allows to quickly test for OS X-specific issues.
According to my bad experience of today, it took longer than 1h30 to get the [Merge] button... Before, it took around 20 min.
Well, it only happed me once. Maybe macOS doesn't like Monday?
Anything in the Allowed Failures section, which is the macOS build and coverage, are totally optional and will not block you from merging. While they may keep the button from being green just to let you know some other things are still running, they won't block you from merging completely (that only happens if the docs or the main test run fail).
Le 26/06/2017 à 15:57, Victor Stinner a écrit :
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?
I see this sporadically on another project. There was no configuration change, it just seems Travis-CI is misbehaving.
Regards
Antoine.
2017-06-27 18:33 GMT+02:00 Antoine Pitrou <antoine@python.org>:
I see this sporadically on another project. There was no configuration change, it just seems Travis-CI is misbehaving.
Oh ok. It's fine in that case.
Today, I didn't see this issue anymore :-) I was usually able to merge in less than 30 min, sometimes less than 20 min.
Victor
participants (3)
-
Antoine Pitrou -
Brett Cannon -
Victor Stinner