AppVeyor was unable to build non-mergeable pull request
Hi,
It's the second time today that I get this error on a PR:
"continuous-integration/appveyor/pr — AppVeyor was unable to build non-mergeable pull request"
With such failure, it's not possible to merge a PR.
The error just occurred on a 2.7 change which is a single commit on top of the update to date 2.7 head: https://github.com/python/cpython/pull/2877
For the other PR, I used the workaround found at: http://help.appveyor.com/discussions/problems/4830-stuck-on-appveyor-was-una...
=> close the PR, reopen the PR
It works around the issue, but it spams Travis CI which has to abort running jobs, and then restarts new jobs from scratch.
$ git log
commit dc72f12b877cacdc3746e152a9379f4c3083fa22 <= my change Author: Victor Stinner <victor.stinner@gmail.com> Date: Wed Jul 26 02:20:55 2017 +0200
bpo-30778: Skip test_bsddb3 on Windows XPcommit 0666d0e50432e3b0109db96b8e48fb6c496bd49c <= upstream HEAD Author: Aditya Hase <aditya@adityahase.com> Date: Wed Jul 26 02:29:52 2017 +0530
bpo-30304: Improve TestCase.assertMultiLineEqual docs (GH-2847)
Mention that TestCase.assertMultiLineEqual method is used bydefault when comparing Unicode string when comparing Unicode strings with assertEqual.
(...)
Victor
So are you requesting we stop building on AppVeyor?
On Tue, Jul 25, 2017, 17:31 Victor Stinner, <victor.stinner@gmail.com> wrote:
Hi,
It's the second time today that I get this error on a PR:
"continuous-integration/appveyor/pr — AppVeyor was unable to build non-mergeable pull request"
With such failure, it's not possible to merge a PR.
The error just occurred on a 2.7 change which is a single commit on top of the update to date 2.7 head: https://github.com/python/cpython/pull/2877
For the other PR, I used the workaround found at:
http://help.appveyor.com/discussions/problems/4830-stuck-on-appveyor-was-una...
=> close the PR, reopen the PR
It works around the issue, but it spams Travis CI which has to abort running jobs, and then restarts new jobs from scratch.
$ git log
commit dc72f12b877cacdc3746e152a9379f4c3083fa22 <= my change Author: Victor Stinner <victor.stinner@gmail.com> Date: Wed Jul 26 02:20:55 2017 +0200
bpo-30778: Skip test_bsddb3 on Windows XPcommit 0666d0e50432e3b0109db96b8e48fb6c496bd49c <= upstream HEAD Author: Aditya Hase <aditya@adityahase.com> Date: Wed Jul 26 02:29:52 2017 +0530
bpo-30304: Improve TestCase.assertMultiLineEqual docs (GH-2847) Mention that TestCase.assertMultiLineEqual method is used bydefault when comparing Unicode string when comparing Unicode strings with assertEqual.
(...)
Victor
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 Tue, Jul 25, 2017, 19:26 Victor Stinner, <victor.stinner@gmail.com> wrote:
2017-07-26 4:22 GMT+02:00 Brett Cannon <brett@python.org>:
So are you requesting we stop building on AppVeyor?
No. I would like to know how to fix the AppVeyor issue :-) Is it a bug under our control?
I don't see how it could be our fault or something we can control for.
Victor
On 7/25/2017 10:22 PM, Brett Cannon wrote:
So are you requesting we stop building on AppVeyor?
Since it runs gui tests, and Travis does not, it is very useful. For the last week, it has mostly always run.
On Tue, Jul 25, 2017, 17:31 Victor Stinner, <victor.stinner@gmail.com <mailto:victor.stinner@gmail.com>> wrote:
Hi, It's the second time today that I get this error on a PR: "continuous-integration/appveyor/pr — AppVeyor was unable to build non-mergeable pull request"
I have seen this too, but seldom.
With such failure, it's not possible to merge a PR.
I believe I was allowed to, but when the new tests are gui tests, it is definitely questionable.
The error just occurred on a 2.7 change which is a single commit on top of the update to date 2.7 head: https://github.com/python/cpython/pull/2877
For the other PR, I used the workaround found at: http://help.appveyor.com/discussions/problems/4830-stuck-on-appveyor-was-unable-to-build-non-mergeable => close the PR, reopen the PR
Thanks for the information.
It works around the issue, but it spams Travis CI which has to abort running jobs, and then restarts new jobs from scratch.
I quit worrying about that.
Terry Jan Reedy
participants (3)
-
Brett Cannon -
Terry Reedy -
Victor Stinner