See <https://builds.apache.org/job/sling-healthcheck-1.6/481/>

------------------------------------------
Started by timer
Building remotely on H10 (Ubuntu ubuntu) in workspace 
<https://builds.apache.org/job/sling-healthcheck-1.6/ws/>
Updating 
http://svn.apache.org/repos/asf/sling/trunk/bundles/extensions/healthcheck at 
revision '2014-09-13T18:11:30.302 +0000'
At revision 1624771
no change for 
http://svn.apache.org/repos/asf/sling/trunk/bundles/extensions/healthcheck 
since the previous build
Parsing POMs
maven3-agent.jar already up to date
maven3-interceptor.jar already up to date
maven3-interceptor-commons.jar already up to date
[healthcheck] $ /home/jenkins/tools/java/latest1.6/bin/java -Xmx512M 
-XX:MaxPermSize=256M -enableassertions -cp 
/home/jenkins/jenkins-slave/maven3-agent.jar:/home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.0.5/boot/plexus-classworlds-2.4.jar
 org.jvnet.hudson.maven3.agent.Maven3Main 
/home/jenkins/jenkins-slave/tools/hudson.tasks.Maven_MavenInstallation/Maven_3.0.5
 /home/jenkins/jenkins-slave/slave.jar 
/home/jenkins/jenkins-slave/maven3-interceptor.jar 
/home/jenkins/jenkins-slave/maven3-interceptor-commons.jar 35944
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Cannot create GC thread. Out of system resources.
# An error report file with more information is saved as:
# 
<https://builds.apache.org/job/sling-healthcheck-1.6/ws/healthcheck/hs_err_pid26539.log>
ERROR: Failed to launch Maven. Exit code = 1

Reply via email to