270409 – [perfs] No JDT/Core tests results in last baseline run

Bug 270409 - [perfs] No JDT/Core tests results in last baseline run

Summary: [perfs] No JDT/Core tests results in last baseline run

Status:	VERIFIED FIXED

Alias:	None

Product:	JDT
Classification:	Eclipse Project
Component:	Core (show other bugs)
Version:	3.5
Hardware:	PC Windows XP

Importance:	P1 major (vote)
Target Milestone:	3.5 M7
Assignee:	Frederic Fusier
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2009-03-30 03:22 EDT by Frederic Fusier
Modified:	2009-04-28 09:59 EDT (History)
CC List:	2 users (show)

See Also:

Attachments
Proposed patch in perf_34x stream (2.29 KB, patch) 2009-03-30 10:48 EDT, Frederic Fusier	no flags	Details \| Diff
View All 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 Frederic Fusier

2009-03-30 03:22:48 EDT

Looking at last nightly build performance results N20090328-2000 relative to R-3.4-200806172000 (200903271816), the JDT/Core tests have no baseline results.

As this is the only component which got this problem I suspect my last changes to fix bug 270257 to be responsible of this issue...

Comment 1 Frederic Fusier

2009-03-30 03:58:40 EDT

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: &apos;buildtest/3.4-perf_200903271816/jdk1.5.0_14/jre/lib/rt.jar&apos; for project &apos;org.eclipse.ui.ide&apos;" type="org.eclipse.jdt.core.JavaModelException">Java Model Exception: Java Model Status [Build path contains duplicate entry: &apos;buildtest/3.4-perf_200903271816/jdk1.5.0_14/jre/lib/rt.jar&apos; for project &apos;org.eclipse.ui.ide&apos;]
	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...

Comment 2 Frederic Fusier

2009-03-30 04:55:01 EDT

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.

Comment 3 Frederic Fusier

2009-03-30 04:57:44 EDT

Kim, would it be possible to have a new baseline run today when this bug was fixed?

Comment 4 Kim Moir

2009-03-30 09:09:56 EDT

Sure, I can run the baselines again once this is fixed.

Comment 5 Frederic Fusier

2009-03-30 10:48:35 EDT

Created attachment 130245 [details]
Proposed patch in perf_34x stream

Comment 6 Frederic Fusier

2009-03-30 10:49:56 EDT

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

Comment 7 Kim Moir

2009-03-30 11:16:34 EDT

Running them now...

Comment 8 Frederic Fusier

2009-03-30 12:32:23 EDT

(In reply to comment #7)
> Running them now...
> 
Thanks :-)

Comment 9 David Audel

2009-04-28 09:59:51 EDT

Verified for 3.5M7