Hi,
Is AppVeyor turned off these days? I don't see a build on https://github.com/python/cpython/pull/2417
Regards
Antoine.
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 python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
On 17 July 2017 at 21:29, Antoine Pitrou <antoine@python.org> 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 | ncoghlan@gmail.com | Brisbane, Australia
On Mon, 17 Jul 2017 at 05:52 Nick Coghlan <ncoghlan@gmail.com> wrote:
On 17 July 2017 at 21:29, Antoine Pitrou <antoine@python.org> 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. ;)
participants (3)
-
Antoine Pitrou -
Brett Cannon -
Nick Coghlan