[python-committers] AppVeyor off?
Hi, Is AppVeyor turned off these days? I don't see a build on https://github.com/python/cpython/pull/2417 Regards Antoine. ___ 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] AppVeyor off?
Nevermind, it seems to have come back online. Le 17/07/2017 à 12:25, Antoine Pitrou a écrit : > > Hi, > > Is AppVeyor turned off these days? I don't see a build on > https://github.com/python/cpython/pull/2417 > > Regards > > Antoine. > ___ > python-committers mailing list > [email protected] > https://mail.python.org/mailman/listinfo/python-committers > Code of Conduct: https://www.python.org/psf/codeofconduct/ > ___ 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] AppVeyor off?
On 17 July 2017 at 21:29, Antoine Pitrou wrote: > > Nevermind, it seems to have come back online. I've occasionally seen that not just with Appveyor, but also with other pre-merge CI systems: it seems like their event monitoring queue and/or task scheduler can get backed up (sometimes significantly), so it takes them a while to report back that they've seen the PR and have a test run scheduled. Travis is the most reliable I've seen when it comes to getting their "Result pending" status back in promptly, so my assumption is that they actually send that back before (or in parallel with) scheduling the CI run itself. 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/
Re: [python-committers] "trivial" label replaced with "skip issue"
On Sun, 16 Jul 2017 at 15:22 Victor Stinner wrote: > 2017-07-16 16:10 GMT+02:00 Victor Stinner : > > What is the benefit of converting old Misc/NEWS entries? > > I guess that the benefit is to use a single format for all NEWS > entries. I understand that it will ease the build of the changelog. > It's to ease backporting since you will never have Misc/NEWS have a merge conflict ever again. > > > Do you have an idea of many files we will get? > > Do we plan to remove old entries? > > Before: 47 files in master. > After: 546 files. Ok, it's not much. > > I didn't know that blurb supports "packing" NEWS entries into a single > file, like Misc/NEWS.d/3.5.0a1.rst which contains 598 entries. Cool! > > My fear was to get 10,000 files in Misc/NEWS and starting to get > performance issues with Git on some platforms. > Yeah, I already had that fear for you. :) > > With the PR #2719 (convert Misc/NEWS to blurb for master), the Git > repository contains 4,340 files. On my laptop, I didn't notice any > major performance related to that. > That was a design goal. ___ 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] AppVeyor off?
On Mon, 17 Jul 2017 at 05:52 Nick Coghlan wrote: > On 17 July 2017 at 21:29, Antoine Pitrou wrote: > > > > Nevermind, it seems to have come back online. > > I've occasionally seen that not just with Appveyor, but also with > other pre-merge CI systems: it seems like their event monitoring queue > and/or task scheduler can get backed up (sometimes significantly), so > it takes them a while to report back that they've seen the PR and have > a test run scheduled. > > Travis is the most reliable I've seen when it comes to getting their > "Result pending" status back in promptly, so my assumption is that > they actually send that back before (or in parallel with) scheduling > the CI run itself. > There's also race condition issues between GitHub's webhook events and when the API actually exposes the data that triggered the webhook (this is why both the Knights Who Say Ni and Bedevere bots have a forced delay before updating a PR). I don't know if AppVeyor heavily delays trying again if the initial status setting fails, but it's possible. I should also mention I try to announce anything that is a visible change to our workflow here, so if I haven't said anything was turned off, assume it broke. ;) ___ python-committers mailing list [email protected] https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
