You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@deltaspike.apache.org by Apache Jenkins Server <je...@builds.apache.org> on 2016/07/31 07:10:43 UTC
Build failed in Jenkins: DeltaSpike_AS7 #957
See <https://builds.apache.org/job/DeltaSpike_AS7/957/changes>
Changes:
[johndament] DELTASPIKE-1176 Support void methods in Futureable
------------------------------------------
Started by upstream project "DeltaSpike for Java EE" build number 82
originally caused by:
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on H11 (docker Ubuntu ubuntu yahoo-not-h2) in workspace <https://builds.apache.org/job/DeltaSpike_AS7/ws/>
> git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
> git config remote.origin.url https://git-wip-us.apache.org/repos/asf/deltaspike.git # timeout=10
Fetching upstream changes from https://git-wip-us.apache.org/repos/asf/deltaspike.git
> git --version # timeout=10
> git -c core.askpass=true fetch --tags --progress https://git-wip-us.apache.org/repos/asf/deltaspike.git +refs/heads/*:refs/remotes/origin/*
> git rev-parse origin/master^{commit} # timeout=10
Checking out Revision 17b3513f69f3546f4b60f8a5ca744644983944a9 (origin/master)
> git config core.sparsecheckout # timeout=10
> git checkout -f 17b3513f69f3546f4b60f8a5ca744644983944a9
> git rev-list 40d24ab50ad1660390d9b06bc5c6ac5cabd84329 # timeout=10
Parsing POMs
Modules changed, recalculating dependency graph
Established TCP socket on 47887
maven32-agent.jar already up to date
maven32-interceptor.jar already up to date
maven3-interceptor-commons.jar already up to date
[DeltaSpike_AS7] $ /home/jenkins/tools/java/latest1.6/bin/java -Xmx2g -Xms256m -XX:MaxPermSize=512m -cp /home/jenkins/jenkins-slave/maven32-agent.jar:/home/jenkins/tools/maven/latest3/boot/plexus-classworlds-2.5.2.jar:/home/jenkins/tools/maven/latest3/conf/logging jenkins.maven3.agent.Maven32Main /home/jenkins/tools/maven/latest3/ /home/jenkins/jenkins-slave/slave.jar /home/jenkins/jenkins-slave/maven32-interceptor.jar /home/jenkins/jenkins-slave/maven3-interceptor-commons.jar 47887
<===[JENKINS REMOTING CAPACITY]===> channel started
ERROR: [JENKINS-18403] JDK 5 not supported to run Maven; retrying with slave Java and setting compile/test properties to point to /home/jenkins/tools/java/latest1.6
Established TCP socket on 51224
maven32-agent.jar already up to date
maven32-interceptor.jar already up to date
maven3-interceptor-commons.jar already up to date
[DeltaSpike_AS7] $ /usr/local/jenkins/java/jdk1.7.0_55/jre/bin/java -Xmx2g -Xms256m -XX:MaxPermSize=512m -cp /home/jenkins/jenkins-slave/maven32-agent.jar:/home/jenkins/tools/maven/latest3/boot/plexus-classworlds-2.5.2.jar:/home/jenkins/tools/maven/latest3/conf/logging jenkins.maven3.agent.Maven32Main /home/jenkins/tools/maven/latest3/ /home/jenkins/jenkins-slave/slave.jar /home/jenkins/jenkins-slave/maven32-interceptor.jar /home/jenkins/jenkins-slave/maven3-interceptor-commons.jar 51224
Error occurred during initialization of VM
java.lang.OutOfMemoryError: unable to create new native thread
ERROR: Failed to launch Maven. Exit code = 1
Jenkins build is back to normal : DeltaSpike_AS7 #958
Posted by Apache Jenkins Server <je...@builds.apache.org>.
See <https://builds.apache.org/job/DeltaSpike_AS7/958/changes>