Ok. I closed https://bugs.python.org/issue31355
Victor
2017-09-23 22:58 GMT+02:00 Antoine Pitrou :
>
> For the record:
> https://blog.travis-ci.com/2017-09-22-macos-update
>
> Regards
>
> Antoine.
>
>
> Le 01/09/2017 à 19:15, Victor Stinner a écrit :
>> Hi,
>>
>> Since today, it seems like the ma
For the record:
https://blog.travis-ci.com/2017-09-22-macos-update
Regards
Antoine.
Le 01/09/2017 à 19:15, Victor Stinner a écrit :
> 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,
On 20 September 2017 at 12:04, Victor Stinner wrote:
> Python tests are very stable on macOS (on buildbots). So yes, it's an issue
> specific to Travis.
Although as Alex explains, that isn't really Travis CI's *fault* -
it's an artifact of the licensing design for macOS being generally
hostile to
Le 20 sept. 2017 00:03, "Barry Warsaw" a écrit :
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?
There were multiple issu
On Sep 19, 2017, at 19:33, Alex Gaynor wrote:
>
> If you find a macOS CI platform with more capacity, please let me know :-)
>
> Travis has been totally underwater of late, but I don't know of any
> alternatives; probably because operating a fleet of macOS builders is a giant
> pain. You need
If you find a macOS CI platform with more capacity, please let me know :-)
Travis has been totally underwater of late, but I don't know of any
alternatives; probably because operating a fleet of macOS builders is a
giant pain. You need Apple hardware, and it turns out you can either
purchase a tra
On Tue, 19 Sep 2017 at 15:04 Barry Warsaw wrote:
> On Sep 19, 2017, at 15:32, Victor Stinner
> 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
On Sep 19, 2017, at 15:32, Victor Stinner 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 Tra
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 mac
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 t
Le 1 sept. 2017 7:24 PM, "Antoine Pitrou" a écrit :
Le 01/09/2017 à 19:15, Victor Stinner a écrit :
>
> Yesterday, it was possible to merge a PR even if the macOS job was
> still queued (no started).
It's still possible today.
Ah? The merge button was disabled whereas AppVeyor and the 2 manda
Le 01/09/2017 à 19:15, Victor Stinner a écrit :
>
> Yesterday, it was possible to merge a PR even if the macOS job was
> still queued (no started).
It's still possible today.
> Maybe we should remove the pre-commit macOS task from the Travis CI
> config to focus on post-commit macOS buildbots?
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 u
13 matches
Mail list logo
