On Mar 2, 4:44 am, Didier Durand <durand.did...@gmail.com> wrote:
> Here it seems that you need only to increase memory parameters for
> your testing job alone not Jenkins as whole: you do that in the "java
> options" line of the build step config of your job: you say -Xms xxx -
> Ymx yyy with appropriate values for X & Y.
I was experiencing OOM with the Hadoop/HBase tests this week.
Increasing the heap within the job didn't help. I ended up changing
the heap/maxperm size across the board (slaves, jenkins start script,
job) and finally got the archiving step to finish. Since I changed
multiple variables at the same time, not sure which was significant,
but with a 4 hr build/test, I gave up trying to find exactly where the
problem was. When I tried just publishing the test results in a test
job (no build, but just untaring a tgz with the test results),
publishing worked fine. Just not after running a real build and test.
I used the following options within the job (via the set "Inject env
variables" properties block), the slave configurations and in the
JENKINS_JAVA_OPTIONS in the /etc/sysconfig/jenkins
-Xms32m -Xmx4096m -XX:MaxPermSize=1024m -XX:
+CMSClassUnloadingEnabled
-Aaron
