Victor Stinner victor.stinner at gmail.com
Wed Jan 24 13:11:32 EST 2018

• Previous message (by thread): [python-committers] AppVeyor is now required to pass on PRs
• Next message (by thread): [python-committers] AppVeyor is now required to pass on PRs
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

Hi,

AppVeyor usually takes between 30 min and 1 hour to check a PR,
whereas Travis CI takes between 10 and 20 minutes (in average,
ignoring rare cases when it's broken). AppVeyor queue is regulary
busy.

Sometimes, I know that my PR is right, because the fix is obvious.
Sometimes, the PR has no impact on Windows. In these cases, the slow
AppVeyor CI can be annoying since it prevents me to merge a PR.

What do you think of making AppVeyor optional again? Careful core
developers should wait for AppVeyor, except if they know that Windows
doesn't matter for a specific PR.

Victor

2018-01-10 21:45 GMT+01:00 Brett Cannon <brett at python.org>:
> I just switched it on to help make sure we don't break on Windows just
> before hitting beta. If it turns out AppVeyor isn't stable enough I will
> switch it back off.
>
> _______________________________________________
> python-committers mailing list
> python-committers at python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>

---

• Previous message (by thread): [python-committers] AppVeyor is now required to pass on PRs
• Next message (by thread): [python-committers] AppVeyor is now required to pass on PRs
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

---

More information about the python-committers mailing list