Community
Participate
Working Groups
I ran the tests on the new hardware. I now get http://download.eclipse.org/e4/downloads/drops/I20100923-1030/results/html/org.eclipse.e4.xwt.tests_linux.gtk.x86_64.html 207 test failures. Invalid thread access junit.framework.AssertionFailedError: Invalid thread access at org.eclipse.e4.xwt.tests.XWTTestCase.runTest(XWTTestCase.java:101) at org.eclipse.e4.xwt.tests.XWTTestCase.runTest(XWTTestCase.java:42) at org.eclipse.e4.xwt.tests.name.NameTests.testName(NameTests.java:26) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:376) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:209) at org.eclipse.test.CoreTestApplication.runTests(CoreTestApplication.java:35) at org.eclipse.test.CoreTestApplication.run(CoreTestApplication.java:31) at org.eclipse.equinox.internal.app.EclipseAppContainer.callMethodWithException(EclipseAppContainer.java:587) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:198) 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:369) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:621) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:576) at org.eclipse.equinox.launcher.Main.run(Main.java:1409) at org.eclipse.equinox.launcher.Main.main(Main.java:1385) at org.eclipse.core.launcher.Main.main(Main.java:34)
http://download.eclipse.org/e4/downloads/drops/I20100923-1030/results/html/org.eclipse.e4.xwt.emf.test_linux.gtk.x86_64.html the XWT EMF tests seem to have the same problem. PW
OK, I'll take care of it. Please indicate me the OS configuration. I just noticed linux.gtk 64 bits. It could be helpful if you can tell me the linux distribution.
Sure, SUSE Linux Enterprise Server 11 (x86_64) VERSION = 11 PATCHLEVEL = 1 Linux 2.6.32.19-0.2-default #1 SMP x86_64 GNU/Linux rpm -q gtk2 gtk2-2.18.9-0.5.1
(In reply to comment #3) > Sure, > > SUSE Linux Enterprise Server 11 (x86_64) > VERSION = 11 > PATCHLEVEL = 1 > > Linux 2.6.32.19-0.2-default #1 SMP x86_64 GNU/Linux > > rpm -q gtk2 > gtk2-2.18.9-0.5.1 Thanks. I'll test it in this environment. I have tested on Ubuntu 64. Here is my environment: Linux: $ uname -a Linux ubuntu 2.6.32-24-generic #43-Ubuntu SMP Thu Sep 16 14:58:24 UTC 2010 x86_64 GNU/Linux GTK $ dpkg -s libgtk2.0-0|grep '^Version' Version: 2.20.1-0ubuntu2 Java: $ java -version java version "1.6.0_20" Java(TM) SE Runtime Environment (build 1.6.0_20-b02) Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01, mixed mode)
I have tested in SuSE using the standard installation SuSE Linux Enterprise 11 SP1. It works as expected. Here is the configuration. Linux: $ uname -a Linux linux-zjpr 2.6.32.12-0.7-default #1 SMP 2010-05-20 11:14:20 +0200 x86_64 x86_64 x86_64 GNU/Linux Java: $ java -version java version "1.6.0_20" Java(TM) SE Runtime Environment (build 1.6.0_20-b02) Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01, mixed mode) GTK $ rpm -q gtk2 gtk2-2.18.9-0.4.1 The version of GTK is little bit different (gtk2-2.18.9-0.4.1, instead of gtk2-2.18.9-0.5.1).
Through the stack trace, it seems a Display is already started by another thread in the same JVM before the launch of the testsuite of XWT. I wonder what are changed in this new environment. The behavior should be same as Linux 32.
(In reply to comment #6) > Through the stack trace, it seems a Display is already started by another > thread in the same JVM before the launch of the testsuite of XWT. > > I wonder what are changed in this new environment. The behavior should be same > as Linux 32. I succeeded in the production of this case by creating a Display on a thread. I have added some code to clean up the existing displays before launch XWT tests. It works in my simulation case.
It is fixed for a while.
