[jbosstools-issues] [JBoss JIRA] (JBIDE-15869) Test failure in org.jboss.tools.cdi.text.ext.test

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-15869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12851516#comment-12851516 ] 

Nick Boldt edited comment on JBIDE-15869 at 11/6/13 1:52 PM:
-------------------------------------------------------------

[~akazakov] What about adding more time to the test plugin timeout? More memory to the job's config? Or just avoiding bad slaves? 

Looks like we have good success on vmg39, but dev84 and dev110 are less effective. 

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/jbosstools-javaee_41/buildTimeTrend

They're all RHEL6 boxes. Wonder how the dev slaves are configured differently from the vmg ones. Can't see anything obvious - looks like the same system props and more or less the same labels are used. 

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/vmg39-rhel6-x86_64/configure-readonly/
vs.
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev84-rhel6-x86_64/configure-readonly/
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/computer/dev110-rhel6-x86_64/configure-readonly/

Maybe [~vjuranek] knows?
                
      was (Author: nickboldt):
    [~akazakov] What about adding more time to the test plugin timeout? More memory to the job's config? Or just avoiding bad slaves? 

Looks like we have good success on vmg39, but dev84 and dev110 are less effective. 

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/jbosstools-javaee_41/buildTimeTrend

They're all RHEL6 boxes. Wonder how the dev slaves are configured differently from the vmg ones. Can't see anything obvious - looks like the same system props and more or less the same labels are used. Maybe [~vjuranek] knows?
                  
> Test failure in org.jboss.tools.cdi.text.ext.test
> -------------------------------------------------
>
>                 Key: JBIDE-15869
>                 URL: https://issues.jboss.org/browse/JBIDE-15869
>             Project: Tools (JBoss Tools)
>          Issue Type: Task
>          Components: cdi
>    Affects Versions: 4.1.1.Beta1
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/jbosstools-javaee_41/120/console}
> 13:39:46 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.18.1:test (default-test) on project org.jboss.tools.cdi.text.ext.test: An unexpected error occured (return code 13). See log for details. -> [Help 1]
> 13:39:46 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-surefire-plugin:0.18.1:test (default-test) on project org.jboss.tools.cdi.text.ext.test: An unexpected error occured (return code 13). See log for details.
> {code}
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/jbosstools-javaee_41/ws/sources/cdi/tests/org.jboss.tools.cdi.text.ext.test/target/work/data/.metadata/.log}
> !ENTRY org.eclipse.osgi 4 0 2013-11-05 11:42:47.049
> !MESSAGE Application error
> !STACK 1
> org.eclipse.swt.SWTError: No more handles [gtk_init_check() failed]{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