Bugzilla – Full Text Bug Listing
| Summary: | create 3.6 baselines for 3.7 performance builds | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Kim Moir <kim.moir> | ||||||||||||||
| Component: | Releng | Assignee: | Kim Moir <kim.moir> | ||||||||||||||
| Status: | RESOLVED FIXED | QA Contact: | |||||||||||||||
| Severity: | major | ||||||||||||||||
| Priority: | P1 | CC: | frederic_fusier, satyam.kandula | ||||||||||||||
| Version: | 3.7 | ||||||||||||||||
| Target Milestone: | 3.7 M1 | ||||||||||||||||
| Hardware: | PC | ||||||||||||||||
| OS: | Windows XP | ||||||||||||||||
| Whiteboard: | |||||||||||||||||
| Attachments: |
|
||||||||||||||||
|
Description
Kim Moir
This is something which must be done as soon as possible because usually the first milestone is the ideal moment to put big and/or high risk changes, hence performances can be dramatically impacted at this early stage of development. As the sooner is the better to detect performance regressions, I think we should not wait too much before restarting the performance runs in 3.7 dvpt stream. So, I'm increasing the priority and the severity of this bug to reflect this urgency... Kim, I hope this is OK for you. TIA Followed this procedure. http://wiki.eclipse.org/Platform-releng-new-baseline branched R3_6 of org.eclipse.releng.eclipsebuilder, org.eclipse.releng.basebuilder, eclipseInternalBuildTools, eclipsePerformanceBuildTools to perf_36x Will attach patches Created attachment 172795 [details]
perf_36x branch patches
Created attachment 172796 [details]
patch for HEAD
Ran a test build and had this error, will investigate on Monday. BUILD FAILED /builds/perf36_201006251555/3.6_perf_36x/eclipsePerformanceBuildTools/all.xml:29: The following error occurred while executing this line: /builds/perf36_201006251555/3.6_perf_36x/org.eclipse.releng.eclipsebuilder/build.xml:35: The following error occurred while executing this line: /builds/perf36_201006251555/3.6_perf_36x/org.eclipse.releng.basebuilder/plugins/org.eclipse.pde.build_3.6.0.v20100603/scripts/build.xml:20: Property mapsRepo was circularly defined. (In reply to comment #3) > Created an attachment (id=172795) [details] > perf_36x branch patches Shouldn't it be: - <condition property="3.5.tested"> - <equals arg1="${testedBuildId}" arg2="3.5" /> + <condition property="3.6.tested"> + <equals arg1="${testedBuildId}" arg2="3.6" /> </condition> instead ? Thanks Frederic, I've fixed the typo Created attachment 172906 [details]
patch to fix mapsRepo issue
Created attachment 172914 [details]
patch
Test build failed this way. Since the p2 bundles don't have performance tests anyways, this patch excludes these bundles from being built in the perf_36x stream.
sdk.tests: Bundle org.eclipse.equinox.p2.tests.discovery_1.0.0.v20100503 failed to resolve.:
Missing required plug-in org.eclipse.equinox.p2.discovery_1.0.0.
Missing required plug-in org.eclipse.equinox.p2.discovery.compatibility_1.0.0.
Missing required plug-in org.eclipse.equinox.p2.ui.discovery_1.0.0.
Created attachment 172959 [details]
more patches
Baseline ran successfully last night. Frederic, can you confirm that the results are as expected? Created attachment 173102 [details]
patches
Okay, I've created the database as well as fixed some other errors in the builder. It looks like there is new data in the perfDb37 database - the baselines are running now. Confirmed that baseline results are in perfDb37. One of the perf machines crashed overnight. I'll run another baseline today to to get a better baseline. Also, I have renabled performance results on our upcoming builds. (In reply to comment #14) > Confirmed that baseline results are in perfDb37. One of the perf machines > crashed overnight. I'll run another baseline today to to get a better > baseline. Also, I have renabled performance results on our upcoming builds. Great news! Thanks Kim :-) |