Build failed in Jenkins: stanbol-trunk-1.6 #332

[Apache Jenkins Server <je...@builds.apache.org>]

See <https://builds.apache.org/job/stanbol-trunk-1.6/332/changes>

Changes:

[suat] STANBOL 296:
-Removed crx-rmi bundle from CMS Adapter
-Removed related entry from the launcher
-Added usage URLRemoteRepository to JCRRepositoryAccess if it is unable to get session with RMIRemoteRepository

------------------------------------------
Started by an SCM change
Building remotely on ubuntu3
Updating http://svn.apache.org/repos/asf/incubator/stanbol/trunk
D         cmsadapter/crx-rmi
U         cmsadapter/launchers/lite/src/main/bundles/list.xml
U         cmsadapter/pom.xml
U         cmsadapter/jcr/src/main/java/org/apache/stanbol/cmsadapter/jcr/repository/JCRRepositoryAccess.java
At revision 1148644
WARNING: clock of the subversion server appears to be out of sync. This can result in inconsistent check out behavior.
ERROR: Ignore Problem expanding maven opts macros org.jenkinsci.plugins.tokenmacro.TokenMacro
Found mavenVersion 2.2.1 from file jar:file:/home/hudson/tools/maven/apache-maven-2.2.1/lib/maven-2.2.1-uber.jar!/META-INF/maven/org.apache.maven/maven-core/pom.properties
[locks-and-latches] Checking to see if we really have the locks
[locks-and-latches] Have all the locks, build can start
Parsing POMs
ERROR: Ignore Problem expanding maven opts macros org.jenkinsci.plugins.tokenmacro.TokenMacro
[trunk] $ /home/hudson/tools/java/latest1.6/bin/java -Xmx1g -XX:MaxPermSize=256M -enableassertions -cp /home/jenkins/jenkins-slave/maven-agent.jar:/home/jenkins/jenkins-slave/classworlds.jar hudson.maven.agent.Main /home/hudson/tools/maven/apache-maven-2.2.1 /x1/jenkins/jenkins-slave/slave.jar /home/jenkins/jenkins-slave/maven-interceptor.jar 46392 /home/jenkins/jenkins-slave/maven2.1-interceptor.jar
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGBUS (0x7) at pc=0xf76ca7a4, pid=6613, tid=4137769840
#
# JRE version: 6.0_20-b02
# Java VM: Java HotSpot(TM) Server VM (16.3-b01 mixed mode linux-x86 )
# Problematic frame:
# C  [libc.so.6+0x1117a4]
#
# An error report file with more information is saved as:
# /x1/jenkins/jenkins-slave/workspace/stanbol-trunk-1.6/trunk/hs_err_pid6613.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
#
[locks-and-latches] Releasing all the locks
[locks-and-latches] All the locks released
ERROR: Failed to launch Maven. Exit code = 134

Jenkins build is back to normal : stanbol-trunk-1.6 #333

[Apache Jenkins Server <je...@builds.apache.org>]

See <https://builds.apache.org/job/stanbol-trunk-1.6/333/changes>