[
https://issues.jboss.org/browse/JBIDE-15579?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-15579:
------------------------------------
Yes, it's probably a jenkins issue.
My first thought was "does this job use Xvnc (usually good) or Xvfb (often bad)
?" But it's configured to use Xvnc, so that SHOULD be fine.
Maybe we need to allocate more memory?
Then again, why does a .core.test need SWT handles? Surely if it's a .core test
there's no UI? Could it be a misconfiguration in the test's pom.xml, which makes
surefire think it's supposed to open UI when it's in fact a headless core test?
org.jboss.tools.seam230.core.test - SWT No More Handles
-------------------------------------------------------
Key: JBIDE-15579
URL:
https://issues.jboss.org/browse/JBIDE-15579
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: seam2
Affects Versions: 4.1.1.Alpha2
Reporter: Nick Boldt
Attachments: console.log
{code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/jbosstools-javaee_41/106/console}
04:28:46 [INFO] org.jboss.tools.seam230.core.test ................. FAILURE [50.907s]
04:28:46 [ERROR] Failed to execute goal
org.eclipse.tycho:tycho-surefire-plugin:0.18.0:test (default-test) on project
org.jboss.tools.seam230.core.test: An unexpected error occured (return code 13). See log
for details. -> [Help 1]
{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