Eh, I believe we have been using this since we decided to use it
in SPARK-17200. (probably you mean Travis CI(?))
It's still two clicks of the mouse to close and reopen :-) but yea I get It
could be bothering and it's a workaround for clarification.
As far as I know, we should open an INFRA JIRA
out of curiosity: why are we using appveyor again?
closing and reopening PRs solely to retrigger builds seems... cumbersome.
shane
On Tue, Jul 24, 2018 at 6:09 PM, Hyukjin Kwon wrote:
> looks we are getting close indeed ...
> Fortunately(?), looks still a bit unusual yet though given the
looks we are getting close indeed ...
Fortunately(?), looks still a bit unusual yet though given the history (
https://ci.appveyor.com/project/ApacheSoftwareFoundation/spark/history)
As far as I know, simple workaround is just to close and reopen the PR and
it retriggers the build. I believe
this
revisiting this thread...
i pushed a small change to some R test code (
https://github.com/apache/spark/pull/21864), and the appveyor build timed
out after 90 minutes:
https://ci.appveyor.com/project/ApacheSoftwareFoundation/spark/build/2440-master
to be honest, i don't have a lot of time to
On Sun, May 13, 2018 at 9:43 PM Hyukjin Kwon wrote:
> From a very quick look, I believe that's just occasional network issue in
> AppVeyor. For example, in this case:
> Downloading:
>
>From a very quick look, I believe that's just occasional network issue in
AppVeyor. For example, in this case:
Downloading:
https://repo.maven.apache.org/maven2/org/scala-lang/scala-compiler/2.11.8/scala-compiler-2.11.8.jar
This took 26ish mins and seems further downloading jars look mins much
Hi dev,
I recently updated an on-going PR [
https://github.com/apache/spark/pull/21092] that was updated with a merge
that included a lot of commits from master and I got the following error:
*continuous-integration/appveyor/pr *— AppVeyor build failed
due to:
*Build execution time has reached