Re: [python-committers] Reminder: snapshots and releases coming up in the next several days
On 9/13/2017 12:35 PM, Ned Deily wrote: 2017-09-18 1200 UTC cutoff: - Python 3.6.3 rc1 Also on 2017-09-18: - Python 3.7.0 alpha 1 Have you branched these off so that further merges go into 3.6.4 and alpha2? ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] Reminder: snapshots and releases coming up in the next several days
On Sep 19, 2017, at 13:55, Terry Reedy wrote: > On 9/13/2017 12:35 PM, Ned Deily wrote: > >> 2017-09-18 1200 UTC cutoff: >> - Python 3.6.3 rc1 > >> Also on 2017-09-18: >> - Python 3.7.0 alpha 1 > > Have you branched these off so that further merges go into 3.6.4 and alpha2? Yes, they were tagged. You can see the history in the cpython log repo (git log) or on the github python/cpython web pages. The release announcement will be forthcoming shortly as the bits arrive from the factories. -- Ned Deily [email protected] -- [] ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] Travis CI: macOS is now blocking -- remove macOS from Travis CI?
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 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.) Victor 2017-09-06 1:30 GMT+02:00 Victor Stinner : > 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 the macOS job: https://bugs.python.org/issue31355 > > Please read the issue for the full rationale. > > Victor > > 2017-09-01 19:15 GMT+02:00 Victor Stinner : >> 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 use "restart job" which >> restarts all tasks, even the completed *and successful* Linux and doc >> jobs. >> >> I have PRs waiting for longer than 2 hours for Travis CI. The macOS >> job is seen as "queued". >> >> Yesterday, it was possible to merge a PR even if the macOS job was >> still queued (no started). >> >> I never wait for macOS, since, as I wrote, it can take longer than 1 >> hour. Moreover, macOS failures are not reported to the GitHub UI :-( >> (Hum, in fact, I'm not sure about that.) >> >> Maybe we should remove the pre-commit macOS task from the Travis CI >> config to focus on post-commit macOS buildbots? If we remove it, >> should we remove it from 2.7, 3.6 and master branches? >> >> We have 3 macOS buildbots: >> >> * x86 Tiger 3.x >> * x86-64 El Capitan 3.x >> * x86-64 Sierra 3.x >> >> All three are currently green ;-) >> >> In the last 3 months, the macOS task of Travis CI caused multiple issues :-/ >> >> Victor ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] Travis CI: macOS is now blocking -- remove macOS from Travis CI?
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 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 [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] Travis CI: macOS is now blocking -- remove macOS from Travis CI?
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 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? > If it is a Travis issue then there are no more resources to throw at it from a Travis perspective: what they are already providing us is rather large and paying out of pocket is rather costly. The only other option is to find another CI provider who has macOS support and use them just for that platform. ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] Travis CI: macOS is now blocking -- remove macOS from Travis CI?
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 trashcan or a mac mini, and neither of those is really designed for a server farm. If anyone here can magically whisper in Tim Cook's ear, can you ask him to license macOS to AWS or Google Cloud or something? :-(, Alex On Tue, Sep 19, 2017 at 7:02 PM, Brett Cannon wrote: > > > 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 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? >> > > If it is a Travis issue then there are no more resources to throw at it > from a Travis perspective: what they are already providing us is rather > large and paying out of pocket is rather costly. The only other option is > to find another CI provider who has macOS support and use them just for > that platform. > > ___ > python-committers mailing list > [email protected] > https://mail.python.org/mailman/listinfo/python-committers > Code of Conduct: https://www.python.org/psf/codeofconduct/ > > -- "I disapprove of what you say, but I will defend to the death your right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire) "The people's good is the highest law." -- Cicero GPG Key fingerprint: D1B3 ADC0 E023 8CA6 ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] Travis CI: macOS is now blocking -- remove macOS from Travis CI?
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 Apple hardware, and it turns out you can either purchase a > trashcan or a mac mini, and neither of those is really designed for a server > farm. > > If anyone here can magically whisper in Tim Cook's ear, can you ask him to > license macOS to AWS or Google Cloud or something? Brett will love my musings: one could imagine a fleet of hackintoshes talking to a flexible CI runner infrastructure as is available on some alternative hosting platforms. Not that I, ahem, know anything about that. Cheers, -Barry signature.asc Description: Message signed with OpenPGP ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] Travis CI: macOS is now blocking -- remove macOS from Travis CI?
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 issues. It was not uncommon that macOS sometimes took 30 min or 1h if not longer. The macOS job was not mandatory. So failures were not reported to GitHub. Moreover, since the job was much slower than the other pre-commit CIs, I never looked at it. Sometimes, the optional macOS job was queue but blocked a PR to be merged. It's a Travis CI bug and I don't want to investigate or report it for the other reasons. Python tests are very stable on macOS (on buildbots). So yes, it's an issue specific to Travis. Victor ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
Re: [python-committers] Travis CI: macOS is now blocking -- remove macOS from Travis CI?
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 the "dynamic worker pool" model typically used for pre-merge CI infrastructure management. macOS is much more amenable to the post-commit model we use for the buildbot fleet, since we're not trying to manage an elastic pool of machines there - we have a static set of machines that work through the merged commits. Cheers, NIck. -- Nick Coghlan | [email protected] | Brisbane, Australia ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
