Github user HyukjinKwon commented on the issue:
https://github.com/apache/spark/pull/15686
@rxin, it seems spurious. The message seems meaning the failure when the
commit is virtually not mergeable[1].
It seems it fails time to time for various reasons. For example, in some
cases, it seems failing to clone due to network problem within AppVeyor.
it is able to re-trigger via Web UI but it seems committers are also not
allowed to access to it. Due to this problem, I temporarily made a bunch of
scripts[3] to manually launch another build via @spark-test account. I can run
the build and leave the comment above until we find a better way to handle it.
(treat me like a bot)
[1]http://help.appveyor.com/discussions/problems/4912-merge-commit-does-not-start-build-in-the-repo-i-make-pull-request-for
[2]https://ci.appveyor.com/project/ApacheSoftwareFoundation/spark/build/256-master
[3]https://github.com/HyukjinKwon/spark-appveyor
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
