11:08 p.m.
[
https://issues.jboss.org/browse/JBIDE-12277?page=com.atlassian.jira.plugi...
]
Snjezana Peco commented on JBIDE-12277:
---------------------------------------
The issue that happens when running modeshape tests is caused by the SWT/GTK
incompatibility. I can't reproduce it locally. It probably happens only on some Linux
distributions. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=376560.
Some tests get aborted and return error 134
-------------------------------------------
Key: JBIDE-12277
URL: https://issues.jboss.org/browse/JBIDE-12277
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, central, FreeMarker, modeshape
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 3.4.0.M1
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:
{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.
#
{code}
Affected jobs:
*
http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job...
*
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:17 a.m.
[
https://issues.jboss.org/browse/JBIDE-12277?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-12277:
----------------------------------------
That's a great clue! If we cannot workaround this issue, we'll probably have to
put more restrictions on slaves we allow to run tests:
So far in error:
* dev03-rhel4-x86
* dspvmg02-rhel4
Some tests get aborted and return error 134
-------------------------------------------
Key: JBIDE-12277
URL: https://issues.jboss.org/browse/JBIDE-12277
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, central, FreeMarker, modeshape
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 3.4.0.M1
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:
{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.
#
{code}
Affected jobs:
*
http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job...
*
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:38 p.m.
[
https://issues.jboss.org/browse/JBIDE-12277?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-12277:
----------------------------------------
Dropping support for RHEL4 (which provide old gtk) for both tests and usage will be
discussed with PM.
Some tests get aborted and return error 134
-------------------------------------------
Key: JBIDE-12277
URL: https://issues.jboss.org/browse/JBIDE-12277
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, central, FreeMarker, modeshape
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 3.4.0.M1
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:
{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.
#
{code}
Affected jobs:
*
http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job...
*
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
8:23 p.m.
[
https://issues.jboss.org/browse/JBIDE-12277?page=com.atlassian.jira.plugi...
]
Snjezana Peco commented on JBIDE-12277:
---------------------------------------
I think that no one test can be executed on RHEL4 because e4 can't be started on that
platform.
I have restricted executing of the central component. Now it runs only on RHEL5 or RHEL6.
Some tests get aborted and return error 134
-------------------------------------------
Key: JBIDE-12277
URL: https://issues.jboss.org/browse/JBIDE-12277
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, central, FreeMarker, modeshape
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 3.4.0.M1
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:
{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.
#
{code}
Affected jobs:
*
http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job...
*
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:49 p.m.
[
https://issues.jboss.org/browse/JBIDE-12277?page=com.atlassian.jira.plugi...
]
Snjezana Peco commented on JBIDE-12277:
---------------------------------------
The archives component had the same issue. I have fixed it.
Some tests get aborted and return error 134
-------------------------------------------
Key: JBIDE-12277
URL: https://issues.jboss.org/browse/JBIDE-12277
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, central, FreeMarker, modeshape
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 3.4.0.M1
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:
{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.
#
{code}
Affected jobs:
*
http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job...
*
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 a.m.
[
https://issues.jboss.org/browse/JBIDE-12277?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-12277:
----------------------------------------
When Max gets back, we'll discuss that and we'll probably remove all RHEL4 in
supported platforms for CI.
Some tests get aborted and return error 134
-------------------------------------------
Key: JBIDE-12277
URL: https://issues.jboss.org/browse/JBIDE-12277
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, central, FreeMarker, modeshape
Reporter: Mickael Istria
Assignee: Mickael Istria
Fix For: 3.4.0.M1
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:
{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.
#
{code}
Affected jobs:
*
http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job...
*
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:08 p.m.
[
https://issues.jboss.org/browse/JBIDE-12277?page=com.atlassian.jira.plugi...
]
Mickael Istria reassigned JBIDE-12277:
--------------------------------------
Assignee: Nick Boldt (was: Mickael Istria)
Seems like RCP apps can work on RHEL4, if the following libs are installed: cairo 1.2.0 +
pango 1.8.2 + glib 2.5.7
Should we ask Jenkins-ops to install those libs on RHEL4, so we can keep on running on all
slaves? Or do we simply drop RHEL4?
Some tests get aborted and return error 134
-------------------------------------------
Key: JBIDE-12277
URL: https://issues.jboss.org/browse/JBIDE-12277
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, central, FreeMarker, modeshape
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 3.4.0.M1
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:
{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.
#
{code}
Affected jobs:
*
http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job...
*
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
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:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:20 a.m.
[
https://issues.jboss.org/browse/JBIDE-12277?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-12277:
-------------------------------
Fix Version/s: 4.0.0.Alpha2
(was: 4.0.0.Alpha1)
Some tests get aborted and return error 134
-------------------------------------------
Key: JBIDE-12277
URL: https://issues.jboss.org/browse/JBIDE-12277
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, central, FreeMarker, modeshape
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 4.0.0.Alpha2
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:
{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.
#
{code}
Affected jobs:
*
http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job...
*
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
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
2:26 a.m.
[
https://issues.jboss.org/browse/JBIDE-12277?page=com.atlassian.jira.plugi...
]
Nick Boldt closed JBIDE-12277.
------------------------------
Fix Version/s: 4.0.0.Alpha1
(was: 4.0.0.Alpha2)
Resolution: Done
RHEL4 is not a supported RUNTIME platform for Eclipse 4.2.
Going to assume there's therefore no point BUILDING (and running tests) on RHEL4
slaves.
Going forward, we should use this label in Jenkins jobs to use only RHEL5 and 6 slaves:
{code}
<assignedNode>(RHEL5||RHEL6)&&!ia64&&!rhts</assignedNode>
{code}
Some tests get aborted and return error 134
-------------------------------------------
Key: JBIDE-12277
URL: https://issues.jboss.org/browse/JBIDE-12277
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, central, FreeMarker, modeshape
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 4.0.0.Alpha1
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:
{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.
#
{code}
Affected jobs:
*
http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job...
*
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
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
2:30 a.m.
[
https://issues.jboss.org/browse/JBIDE-12277?page=com.atlassian.jira.plugi...
]
Nick Boldt updated JBIDE-12277:
-------------------------------
Fix Version/s: 4.0.0.Alpha2
(was: 4.0.0.Alpha1)
Some tests get aborted and return error 134
-------------------------------------------
Key: JBIDE-12277
URL: https://issues.jboss.org/browse/JBIDE-12277
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, central, FreeMarker, modeshape
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 4.0.0.Alpha2
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:
{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.
#
{code}
Affected jobs:
*
http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job...
*
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
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
2:30 a.m.
[
https://issues.jboss.org/browse/JBIDE-12277?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-12277:
------------------------------------
Turns out a lot of jobs are still set to run on RHEL4, so I have some work to do here to
update the job configs. Reopening and moving to Alpha2. :(
Some tests get aborted and return error 134
-------------------------------------------
Key: JBIDE-12277
URL: https://issues.jboss.org/browse/JBIDE-12277
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, central, FreeMarker, modeshape
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 4.0.0.Alpha2
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:
{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.
#
{code}
Affected jobs:
*
http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job...
*
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
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
11:20 a.m.
[
https://issues.jboss.org/browse/JBIDE-12277?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-12277:
----------------------------------------
I think I already made this change several times too, and noticed that I always find some
remaining jobs using RHEL... I'm wondering whether you and I are using the same SVN
folder for Jenkins cache. If not, we may have some sync problems that cause some changes
to be overwritten later (although the update/pull/modify/push/commit process should
prevent from it).
I do use the >https://jenkins.mw.lab.eng.bos.redhat.com/hudson/ URL in hudson-sync
job.
Some tests get aborted and return error 134
-------------------------------------------
Key: JBIDE-12277
URL: https://issues.jboss.org/browse/JBIDE-12277
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, central, FreeMarker, modeshape
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 4.0.0.Alpha2
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:
{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.
#
{code}
Affected jobs:
*
http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job...
*
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
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
7:46 p.m.
[
https://issues.jboss.org/browse/JBIDE-12277?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-12277:
------------------------------------
Since returning from my PTO (and pulling down your patch in github to make the tool work
w/ the new authentication mechanism), I only use cache in
https://svn.jboss.org/repos/devstudio/trunk/hudson-jobs/cache/https/jenki...
-- eventually we should deprecate the old folders under
https://svn.jboss.org/repos/devstudio/trunk/hudson-jobs/cache/https/hudso....
I'll be tweaking jobs again today to remove my github watch thing and kicking out more
RHEL4 references.
Some tests get aborted and return error 134
-------------------------------------------
Key: JBIDE-12277
URL: https://issues.jboss.org/browse/JBIDE-12277
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, central, FreeMarker, modeshape
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 4.0.0.Alpha2
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:
{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.
#
{code}
Affected jobs:
*
http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job...
*
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
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
3:41 a.m.
[
https://issues.jboss.org/browse/JBIDE-12277?page=com.atlassian.jira.plugi...
]
Nick Boldt closed JBIDE-12277.
------------------------------
Resolution: Done
None of the component or aggregate jobs run on RHEL4 any more. Closing
Some tests get aborted and return error 134
-------------------------------------------
Key: JBIDE-12277
URL: https://issues.jboss.org/browse/JBIDE-12277
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, central, FreeMarker, modeshape
Reporter: Mickael Istria
Assignee: Nick Boldt
Fix For: 4.0.0.Alpha2
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:
{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.
#
{code}
Affected jobs:
*
http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job...
*
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
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
4391
days inactive
4463
days old
jbosstools-issues@lists.jboss.org
17 comments
3 participants
participants (3)
-
Mickael Istria (JIRA) -
Nick Boldt (JIRA)
-
Snjezana Peco (JIRA)