Thanks Wes. I didn't know that we can enable Appveyor build on our fork.
On Mon, Jul 31, 2017 at 10:18 PM, Wes McKinney <wesmck...@gmail.com> wrote: > Also, if you aren't touching any C++ or Python code (or associated CI > scripts), you can generally ignore the Appveyor build result. > > On Tue, Aug 1, 2017 at 1:09 AM, Wes McKinney <wesmck...@gmail.com> wrote: > > hi Siddharth, > > > > Appveyor seems especially bad today, this is the worst I've seen it > > backed up in a while. I'm partially responsible for triggering more > > builds today than usual. But in general, this can happen now and then. > > Because we are in the queue with all the other ASF projects sometimes > > it can take several hours for builds on the ASF account to run. > > > > You can generally get faster builds by enabling Appveyor on your fork; > > on normal days Appveyor jobs will start up right away and finish in > > under an hour, e.g. https://ci.appveyor.com/project/wesm/arrow/history > > > > - Wes > > > > > > On Tue, Aug 1, 2017 at 1:06 AM, Siddharth Teotia <siddha...@dremio.com> > wrote: > >> Hi All, > >> > >> I created a PR 4 hours ago and the AppVeyor build still hasn't finished. > >> The Travis CI build ran fine. > >> > >> Is this expected? I am surprised since for all my previous PRs, both > checks > >> used to get done in 1-2 hours. > >> > >> In fact, the 3 latest 3 PRs (923, 924, 925) are in a similar situation. > >> > >> Thanks, > >> Siddharth >
