[jbosstools-issues] [JBoss JIRA] (JBIDE-19750) Install grinder fails to run on RHEL7: No more handles!
[
https://issues.jboss.org/browse/JBIDE-19750?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-19750:
----------------------------------------
With those property set, we now get
{code}
09:00:43 !MESSAGE Internal browser is not available: No more handles
[MOZILLA_FIVE_HOME='/qa/tools/opt/firefox-5'] (java.lang.UnsatisfiedLinkError:
Could not load SWT library. Reasons:
09:00:43
/qa/hudson_workspace/workspace/jbosstools-install-grinder.install-tests.matrix_master/ba86289f/eclipse/configuration/org.eclipse.osgi/705/0/.cp/libswt-mozilla-gtk-4517.so:
libxpcom.so: cannot open shared object file: No such file or directory
09:00:43 no swt-mozilla-gtk in java.library.path
09:00:43 /qa/services/hudson/.swt/lib/linux/x86_64/libswt-mozilla-gtk-4517.so:
libxpcom.so: cannot open shared object file: No such file or directory
09:00:43 Can't load library:
/qa/services/hudson/.swt/lib/linux/x86_64/libswt-mozilla-gtk.so
09:00:43 )
{code}
Install grinder fails to run on RHEL7: No more handles!
-------------------------------------------------------
Key: JBIDE-19750
URL: https://issues.jboss.org/browse/JBIDE-19750
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Affects Versions: 4.3.0.Beta1
Reporter: Nick Boldt
Assignee: Mickael Istria
{code}
16:48:30 Installing org.eclipse.swtbot.eclipse.test.junit.feature.group
2.2.1.201402241301.
...
13:39:08 !MESSAGE Internal browser is not available: No more handles [Browser style
SWT.MOZILLA and Java system property org.eclipse.swt.browser.DefaultType=mozilla are not
supported with GTK 3 as XULRunner is not ported for GTK 3 yet]
13:43:18 Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 253.079 sec
13:43:18
13:43:18 Testcase: testInstall took 252.166 sec
{code} -
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
I tried to run using `-Dorg.eclipse.swt.browser.DefaultType=webkit` as a script param for
`testInstall.groovy` but it must not have passed through to the eclipse install process,
as the above error suggests.
Wondering if ...
a) passing through a different *swt.browser.DefaultType*, &/or
b) using a newer SWTBot (which works with Luna [1] now?)
... might help.
[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=464619
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)