There are both Debug and Release configurations here

https://github.com/apache/arrow/blob/master/ci/appveyor-cpp-build.bat#L32

If you try those CMake commands in your VM, you do not reproduce the issue?

On Wed, Feb 20, 2019 at 5:01 AM Micah Kornfield <emkornfi...@gmail.com> wrote:
>
> I seem to recall at least one appveyor job passing (which seems to
> correspond with my ability to get a build on windows passing), but it is
> hard to tell because appveyor cancels all other jobs once one fails.
>
> On Wed, Feb 20, 2019 at 2:44 AM Antoine Pitrou <anto...@python.org> wrote:
>
> >
> > Hi Micah,
> >
> > Le 20/02/2019 à 11:30, Micah Kornfield a écrit :
> > > I've been working on a PR [1] that passes CI under linux/mac builds (when
> > > the master build isn't broken).  I've been able to run it locally (linux
> > > VM), using both ASAN and Valgrind without issues.  But I'm getting
> > > consistent errors (looks like a segfault) when building on windows on
> > under
> > > static_crt_build [2].  I can't seem to get that version of the build
> > > working on a Windows 10 VM with MSVC 2017 (it does pass when i follow the
> > > normal windows build instructions with Ninja and CLcache [3]).
> > >
> > > I would appreciate help in any of the following ways (and other
> > suggestions
> > > welcome):
> > > 1.  Give detailed instructions on how to replicate the static_crt_build
> > > appveyor build in a VM (I use virtual box).
> > > 2.  Take a look at the pull request to see if they can spot anything I'm
> > > doing wrong.
> > > 3.  Try to replicate this locally in there own Windows setup.
> > > 4.  General advice on what might cause this type of disparity (or suggest
> > > cmake flags on linux that might give s similar issue).
> >
> > Does this happen on other AppVeyor jobs or only the static CRT build?
> >
> > Regards
> >
> > Antoine.
> >

Reply via email to