Community
Participate
Working Groups
In this build: http://build.eclipse.org/webtools/committers/wtp-R3.2.0-I/20100211150852/I-3.2.0-20100211150852/ Which we are supposed to promote today. While the JAXWS smoketest/promotion page was checked "ok" no mention was made of this failing unit test. Is it a problem with test? Code? unknown? Below is the stack trace list in log: junit.framework.AssertionFailedError at org.eclipse.jst.ws.jaxws.dom.runtime.tests.dom.persistence.sync.ModelSynchronizationTests.test_deletedCUWithSeiSynched(ModelSynchronizationTests.java:222) at org.jmock.core.VerifyingTestCase.runBare(VerifyingTestCase.java:39) at org.eclipse.jst.ws.jaxws.testutils.jmock.MockObjectTestCase.runBareInternal(MockObjectTestCase.java:49) at org.eclipse.jst.ws.jaxws.testutils.jmock.testcases.BeforeAfterEnabler.runBare(BeforeAfterEnabler.java:42) at org.eclipse.jst.ws.jaxws.testutils.jmock.MockObjectTestCase.runBare(MockObjectTestCase.java:55) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:376) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:209) at org.eclipse.test.UITestApplication$3.run(UITestApplication.java:195) at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3501) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3148) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2407) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2371) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2220) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:500) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:493) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) 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.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:367) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:611) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:566) at org.eclipse.equinox.launcher.Main.run(Main.java:1363) at org.eclipse.equinox.launcher.Main.main(Main.java:1339)
It's a test problem. Sorry I missed that in the logs last night when smoke testing.
Created attachment 159058 [details] consolelog consolelog attached
Test commented out for now. Danail is this a duplicate of Bugs 302034 302033 ? Those changes hadn't been released for this build.
I assume that the reason is the very same as in the bugs mentioned - resource changes directly in the main thread. However, I am not closing the bug as duplicate because the test itself should be modified to fork in new thread when deleting compilation units. I will provide the relevant fix in the test. Regards, Danail
Fix committed in HEAD and released as v201002220723
