Ben Caradoc-Davies ha scritto: > Hudson for GeoServer also uses -Dtest.maxHeapSize=256M, which is half > the default set in the main pom. Can we remove this option for > GeoServer? I expect major grief if we try to run app-schema unit tests > while this option is present.
I think we added that option to avoid straining the build server, it does not have _that_ many resources (it's a VM so it only gets a slice of the real hardware). I also find it a bit problematic that the thing requires so much memory. Back then when working with Windows I used to start GS with the default heap (64MB) and reported any OOM that would occur as a bug. But I know that other devs give it 256MB at the very least. > The continuous integration engine should be consistent with the pom, > otherwise developers will run local tests, run their own CI, and commit > code which fails to build on Hudson. Hmmm... let's make the default pom use 256MB then? ;-) Seriously, we may look in having the build server use more memory for some time (mind, this may well end up having the build server go in a swap storm as a result) but I really feel a plan to avoid GS becoming more of a memory hog should be on the table. Cheers Andrea -- Andrea Aime OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
