Bug 309473 - JUnit failure AssertionFailedError: pdomName in managedbuilder.tests.suite
Summary: JUnit failure AssertionFailedError: pdomName in managedbuilder.tests.suite
Status: ASSIGNED
Alias: None
Product: CDT
Classification: Tools
Component: cdt-build-managed (show other bugs)
Version: 7.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: cdt-build-inbox@eclipse.org CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-16 09:59 EDT by Andrew Gvozdev CLA
Modified: 2020-09-04 15:17 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Gvozdev CLA 2010-04-16 09:59:52 EDT 
See http://download.eclipse.org/tools/cdt/builds/7.0.0/I.I201004160805/junits.html#org.eclipse.cdt.managedbuilder.tests.suite

junit.framework.AssertionFailedError: pdomName
at org.eclipse.cdt.projectmodel.tests.CProjectDescriptionSerializationTests.testPersistentProperties(CProjectDescriptionSerializationTests.java:202)
at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:376)
at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:209)
at org.eclipse.test.UITestApplication$2.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:3507)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3154)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2416)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2380)
at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2229)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:504)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:497)
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:196)
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:619)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574)
at org.eclipse.equinox.launcher.Main.run(Main.java:1406)
at org.eclipse.equinox.launcher.Main.main(Main.java:1382)
at org.eclipse.core.launcher.Main.main(Main.java:34)

My guess is that it is concurrency issue. Will monitor if it occurs in future weekly builds.