Windows builds failing

[Dan Smith <ds...@pivotal.io>]

It looks like all of the windows jobs are failing. The code changes between
the failed job and the passed job don't seem like they could be related,
did something else change?

https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/WindowsUnitTest/builds/70

-Dan

Re: Windows builds failing

[Jens Deppe <jd...@pivotal.io>]

That went in a few days ago so this run is already using that.

On Fri, Aug 24, 2018 at 2:49 PM Jacob Barrett <jb...@pivotal.io> wrote:

> Dan just merged a change to gradle that drops the scanner plugin that
> seems to suck up a ton of ram.
>
> > On Aug 24, 2018, at 2:38 PM, Jens Deppe <jd...@pivotal.io> wrote:
> >
> > Not in the build process.
> >
> > Having them all fail simultaneously is very suspicious though. I
> restarted
> > one of them and it ran fine.
> >
> > We're about to switch the build model for Windows to match the linux
> builds
> > where a 'heavy lifter' is spawned for each job. During my testing of
> that I
> > found the Gradle daemon still running out of memory and I needed to bump
> > its heap to 4GB. I'm wondering if there's a memory issue here as well but
> > just not getting logged as such.
> >
> > --Jens
> >
> >> On Fri, Aug 24, 2018 at 1:32 PM Dan Smith <ds...@pivotal.io> wrote:
> >>
> >> It looks like all of the windows jobs are failing. The code changes
> between
> >> the failed job and the passed job don't seem like they could be related,
> >> did something else change?
> >>
> >>
> >>
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/WindowsUnitTest/builds/70
> >>
> >> -Dan
> >>
>

Re: Windows builds failing

[Jacob Barrett <jb...@pivotal.io>]

Dan just merged a change to gradle that drops the scanner plugin that seems to suck up a ton of ram.

> On Aug 24, 2018, at 2:38 PM, Jens Deppe <jd...@pivotal.io> wrote:
> 
> Not in the build process.
> 
> Having them all fail simultaneously is very suspicious though. I restarted
> one of them and it ran fine.
> 
> We're about to switch the build model for Windows to match the linux builds
> where a 'heavy lifter' is spawned for each job. During my testing of that I
> found the Gradle daemon still running out of memory and I needed to bump
> its heap to 4GB. I'm wondering if there's a memory issue here as well but
> just not getting logged as such.
> 
> --Jens
> 
>> On Fri, Aug 24, 2018 at 1:32 PM Dan Smith <ds...@pivotal.io> wrote:
>> 
>> It looks like all of the windows jobs are failing. The code changes between
>> the failed job and the passed job don't seem like they could be related,
>> did something else change?
>> 
>> 
>> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/WindowsUnitTest/builds/70
>> 
>> -Dan
>> 

Re: Windows builds failing

[Jens Deppe <jd...@pivotal.io>]

Not in the build process.

Having them all fail simultaneously is very suspicious though. I restarted
one of them and it ran fine.

We're about to switch the build model for Windows to match the linux builds
where a 'heavy lifter' is spawned for each job. During my testing of that I
found the Gradle daemon still running out of memory and I needed to bump
its heap to 4GB. I'm wondering if there's a memory issue here as well but
just not getting logged as such.

--Jens

On Fri, Aug 24, 2018 at 1:32 PM Dan Smith <ds...@pivotal.io> wrote:

> It looks like all of the windows jobs are failing. The code changes between
> the failed job and the passed job don't seem like they could be related,
> did something else change?
>
>
> https://concourse.apachegeode-ci.info/teams/main/pipelines/develop/jobs/WindowsUnitTest/builds/70
>
> -Dan
>