I think that the memory allocated to hudson isn't really important. We set memory settings in Maven builds using MAVEN_OPTS. For Maven-Plugins, we have -Xmx512m in MAVEN_OPTS
Arnaud On Wed, Aug 6, 2008 at 11:22 PM, Benjamin Bentmann < [EMAIL PROTECTED]> wrote: > Arnaud HERITIER wrote: > > Ok the build takes approximatively 3 hours (and is launched every 4 >> hours) >> which isn't very nice to do continuous integration. >> > > Sure, Brian told me that Hudson was not a dedicated machine but I still > wonder whether this long build time is normal. For instance, both > https://ci.sonatype.org/job/Maven-Plugins-ITs/179/console and > https://ci.sonatype.org/job/Maven-Plugins-ITs/178/console > crashed during startup with an OutOfMemoryError. In particular, #179 > reported "GC overhead limit exceeded". > > Also, > https://ci.sonatype.org/job/maven-shared/204/ > took only 4 minutes, while the last one > https://ci.sonatype.org/job/maven-shared/210/ > took 12 minutes. > > Can it be that Hudson's JVM is running low on memory and as a consequence > spends lots of time doing GC to reclaim the few bytes is has, occasionally > failing as reported? > > > Benjamin > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- .......................................................... Arnaud HERITIER .......................................................... OCTO Technology - aheritier AT octo DOT com www.octo.com | blog.octo.com .......................................................... ASF - aheritier AT apache DOT org www.apache.org | maven.apache.org ...........................................................
