[dash-dev] Athena: tests randomly failing to run on build.eclipse.org, w

[Nicolas Bros <nbros.mia@xxxxxxxxx>]

Hi again,

My Athena build failed to run its tests from time to time, with a seemingly random frequency.
I think it happens when someone else's build is running concurrently on the build server (build.eclipse.org).






All the build log says is:
[exec] java-test:
     [exec]      [echo] Running org.eclipse.gmt.modisco.tests.AllTests. Result file: /opt/users/hudsonbuild/.hudson/jobs/cbi-modisco-nightly/workspace/build/N200912110239/testing/target/eclipse/results/org.eclipse.gmt.modisco.tests.AllTests.xml.







     [exec]      [java] Java Result: 13

But I went looking in the test workspace log, and I saw the following exception:

org.eclipse.swt.SWTError: No more handles [gtk_init_check() failed]






        at org.eclipse.swt.SWT.error(SWT.java:3910)
        at org.eclipse.swt.widgets.Display.createDisplay(Display.java:863)







        at org.eclipse.swt.widgets.Display.create(Display.java:851)






        at org.eclipse.swt.graphics.Device.<init>(Device.java:152)






        at org.eclipse.swt.widgets.Display.<init>(Display.java:479)







        at org.eclipse.swt.widgets.Display.<init>(Display.java:470)






        at org.eclipse.ui.internal.Workbench.createDisplay(Workbench.java:532)






        at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:161)







        at org.eclipse.ui.internal.ide.application.IDEApplication.createDisplay(IDEApplication.java:143)






        at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:88)






        at org.eclipse.test.UITestApplication.runApplication(UITestApplication.java:138)







        at org.eclipse.test.UITestApplication.run(UITestApplication.java:60)






        at org.eclipse.test.UITestApplication.start(UITestApplication.java:210)






        at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:194)







        at org.eclipse.equinox.internal.app.MainApplicationLauncher.run(MainApplicationLauncher.java:32)






        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)







        at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)






        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:368)






        at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179)







        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)






        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79)






        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)







        at java.lang.reflect.Method.invoke(Method.java:618)
        at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:559)






        at org.eclipse.equinox.launcher.Main.basicRun(Main.java:514)






        at org.eclipse.equinox.launcher.Main.run(Main.java:1311)







        at org.eclipse.equinox.launcher.Main.main(Main.java:1287)
        at org.eclipse.core.launcher.Main.main(Main.java:34)






Has anyone here encountered the same problem?
It looks like this is related to bug 106396.
A workaround mentioned in this bug is to use the JAVA_HIGH_ZIPFDS variable, which tells the IBM JDK to use more file descriptors.






I have added this line in my Hudson script:
export JAVA_HIGH_ZIPFDS=500
And after several successful builds, I can say that this seems to have solved the problem.



-- 
Nicolas Bros
R&D
tel: 06 75 09 19 88


nbros@xxxxxxxxxxxxxxxx
nbros.mia@xxxxxxxxx
Mia-Software, 410 clos de la Courtine
93160 Noisy-le-Grand
http://www.mia-software.com






.: model driven agility :.