Change By: Mickael Istria (02/Jul/12 5:36 AM)
Description: Some jobs on CI are failing with error code *134*
This means that JVM crashed, here is what we can read in logs about this crash:
{
quote code }
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x0062c453, pid=19100, tid=3074149280
#
# JRE version: 6.0_30-b12
# Java VM: Java HotSpot(TM) Server VM (20.5-b03 mixed mode linux-x86 )
# Problematic frame:
# C  [libc.so.6+0x6b453]  unsigned long+0x23
#
# An error report file with more information is saved as:
# /qa/hudson_ws/workspace/jbosstools-3.3_trunk.component--freemarker/sources/tests/org.jboss.ide.eclipse.freemarker.test/hs_err_pid19100.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
{
quote code }

Affected jobs:
* http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-3.3_trunk.component--central/507/console
* https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job/jbosstools-3.3_trunk.component--freemarker/951/console

This does not seem deterministic as for freemarker, the exactly same job 
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira