[jbosstools-issues] [JBoss JIRA] (JBIDE-13854) intermittent install-grinder test failures caused by SIGSEGV

Nick Boldt (JIRA) jira-events at lists.jboss.org
Mon Mar 25 17:50:42 EDT 2013


     [ https://issues.jboss.org/browse/JBIDE-13854?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Boldt updated JBIDE-13854:
-------------------------------

    Summary: intermittent install-grinder test failures caused by SIGSEGV  (was: intermittent install-grinter test failures caused by SIGSEGV)

    
> intermittent install-grinder test failures caused by SIGSEGV
> ------------------------------------------------------------
>
>                 Key: JBIDE-13854
>                 URL: https://issues.jboss.org/browse/JBIDE-13854
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: testing-tools
>    Affects Versions: 4.1.0.Alpha2
>            Reporter: Nick Boldt
>            Assignee: Mickael Istria
>
> When run on https://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dsp06-rhel5-x86_64/, this build failed:
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_6.0.juno/job/jbosstools-4.0_stable_branch.install-tests.matrix/INSTALL_PLAN=http%3A%2F%2Fwww.qa.jboss.com%2Fbinaries%2FRHDS%2Fupdates%2Fdevelopment%2F6.0.1.CR1a.core%3Bhttp%3A%2F%2Fwww.qa.jboss.com%2Fbinaries%2FRHDS%2Fupdates%2Fdevelopment%2F6.0.1.CR1a.core%2Fdevstudio-directory.xml,eclipseBundleVersion=juno.R,label_exp=%28RHEL5||RHEL6%29%26%26!ia64%26%26!rhts/92/console}
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments:  -application org.eclipse.swtbot.eclipse.junit4.headless.swtbottestapplication -testApplication org.eclipse.ui.ide.workbench -product org.eclipse.epp.package.jee.product formatter=org.apache.tools.ant.taskdefs.optional.junit.XMLJUnitResultFormatter,TEST-install-2013032310-1006.xml formatter=org.apache.tools.ant.taskdefs.optional.junit.PlainJUnitResultFormatter -testPluginName org.jboss.tools.tests.installation -className org.jboss.tools.tests.installation.InstallFromCentralTest
> Command-line arguments:  -application org.eclipse.swtbot.eclipse.junit4.headless.swtbottestapplication -testApplication org.eclipse.ui.ide.workbench -product org.eclipse.epp.package.jee.product -data workspace formatter=org.apache.tools.ant.taskdefs.optional.junit.XMLJUnitResultFormatter,TEST-install-2013032310-1006.xml formatter=org.apache.tools.ant.taskdefs.optional.junit.PlainJUnitResultFormatter -testPluginName org.jboss.tools.tests.installation -className org.jboss.tools.tests.installation.InstallFromCentralTest -consoleLog -debug
> !ENTRY org.eclipse.osgi 2 1 2013-03-23 10:07:15.646
> !MESSAGE NLS missing message: JBossRuntimeStartup_JBoss_EAP_Server_6_1 in: org.jboss.ide.eclipse.as.core.Messages
> Testsuite: org.jboss.tools.tests.installation.InstallFromCentralTest
> Application Started: 24573
> log4j:WARN No appenders could be found for logger (org.eclipse.swtbot.swt.finder.matchers.AbstractMatcher).
> log4j:WARN Please initialize the log4j system properly.
> !ENTRY org.eclipse.ui.browser 2 0 2013-03-23 10:07:23.217
> !MESSAGE Internal browser is not available: XPCOM error 0x80004003
> #
> # A fatal error has been detected by the Java Runtime Environment:
> #
> #  SIGSEGV (0xb) at pc=0x0000003420c08b9b, pid=17450, tid=1076410688
> #
> # JRE version: 6.0_43-b01
> # Java VM: Java HotSpot(TM) 64-Bit Server VM (20.14-b01 mixed mode linux-amd64 compressed oops)
> # Problematic frame:
> # C  [ld-linux-x86-64.so.2+0x8b9b]
> #
> # An error report file with more information is saved as:
> # /qa/local/hudson_workspace/workspace/jbosstools-4.0_stable_branch.install-tests.matrix/cdf6d04c/eclipse/hs_err_pid17450.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}

--
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


More information about the jbosstools-issues mailing list