Looks like we are having a similar problem with 17.x. Perhaps there is
something special about 1st-time builds that consumes more memory than
usual?
Torben
On Fri, Oct 14, 2016 at 6:22 PM, Ben Caradoc-Davies <b...@transient.nz>
wrote:
> Success! Build #3 passed without any extra JVM args. Was the extra
> memory really needed? A mystery.
>
> On 15/10/16 12:44, Ben Caradoc-Davies wrote:
> > This fixed the build. We have some new commits on 16.x, so I have undone
> > this change to see if the deploy step passes without it.
> >
> > On 15/10/16 10:00, Ben Caradoc-Davies wrote:
> >> Failed in the deploy step. I set -Xmx1024m and kicked it. I seem to
> >> recall that new builds sometimes require a little help (and more memory)
> >> to get past the first build. We can then remove the JVM option.
> >>
> >> On 15/10/16 05:18, moni...@boundlessgeo.com wrote:
> >>> See <http://ares.boundlessgeo.com/jenkins/job/geotools-16.x/1/>
> >>
> >
>
> --
> Ben Caradoc-Davies <b...@transient.nz>
> Director
> Transient Software Limited <http://transient.nz/>
> New Zealand
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
