Bugzilla – Full Text Bug Listing
| Summary: | [perfs] No JDT/Core tests results in last baseline run | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] JDT | Reporter: | Frederic Fusier <frederic_fusier> | ||||
| Component: | Core | Assignee: | Frederic Fusier <frederic_fusier> | ||||
| Status: | VERIFIED FIXED | QA Contact: | |||||
| Severity: | major | ||||||
| Priority: | P1 | CC: | david_audel, kim.moir | ||||
| Version: | 3.5 | ||||||
| Target Milestone: | 3.5 M7 | ||||||
| Hardware: | PC | ||||||
| OS: | Windows XP | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Frederic Fusier
My assumption was correct, it's a side effect of fix for bug 270257. There's an error while setting projects classpath: <testcase classname="org.eclipse.jdt.core.tests.performance.FullSourceWorkspaceSearchTests" name="testIndexing" time="28.525"> <error message="Build path contains duplicate entry: 'buildtest/3.4-perf_200903271816/jdk1.5.0_14/jre/lib/rt.jar' for project 'org.eclipse.ui.ide'" type="org.eclipse.jdt.core.JavaModelException">Java Model Exception: Java Model Status [Build path contains duplicate entry: 'buildtest/3.4-perf_200903271816/jdk1.5.0_14/jre/lib/rt.jar' for project 'org.eclipse.ui.ide'] at org.eclipse.jdt.internal.core.JavaModelOperation.runOperation(JavaModelOperation.java:766) at org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:2815) at org.eclipse.jdt.internal.core.JavaProject.setRawClasspath(JavaProject.java:2846) at org.eclipse.jdt.core.tests.performance.FullSourceWorkspaceTests.setUpFullSourceWorkspace(FullSourceWorkspaceTests.java:676) at org.eclipse.jdt.core.tests.performance.FullSourceWorkspaceTests.setUp(FullSourceWorkspaceTests.java:569) at org.eclipse.jdt.core.tests.performance.FullSourceWorkspaceSearchTests.setUp(FullSourceWorkspaceSearchTests.java:81) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:354) at org.eclipse.test.EclipseTestRunner.run(EclipseTestRunner.java:206) 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:574) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:195) 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:382) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:549) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) at org.eclipse.equinox.launcher.Main.run(Main.java:1236) at org.eclipse.equinox.launcher.Main.main(Main.java:1212) at org.eclipse.core.launcher.Main.main(Main.java:30) </error> However, I did run tests before releasing this change and didn't get any error... and I still cannot reproduce locally!? I'll investigate further... I can now reproduce it... It's because I used HEAD stream for other JDT/Core projects in my workspace instead of using the v_874 version as it's done while running baseline. Kim, would it be possible to have a new baseline run today when this bug was fixed? Sure, I can run the baselines again once this is fixed. Created attachment 130245 [details]
Proposed patch in perf_34x stream
Released for 3.5M7 in perf_34x stream. The jdtcore.map file has also been updated in same stream... Kim, I'm ready for a new baseline run :-) TIA Running them now... (In reply to comment #7) > Running them now... > Thanks :-) Verified for 3.5M7 |