| Summary: | Baseline is not valid while generating performance results for maintenance builds | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Frederic Fusier <frederic_fusier> | ||||
| Component: | Releng | Assignee: | Frederic Fusier <frederic_fusier> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | critical | ||||||
| Priority: | P3 | CC: | kim.moir | ||||
| Version: | 3.6 | ||||||
| Target Milestone: | 3.6.1 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Frederic Fusier
The problem comes from the fact that some 3.6 baseline runs results were put in the 3.6 performance database. These results makes the perf results generator crazy and fails to use the correct baseline. I'll release a patch soon... Created attachment 173776 [details]
Proposed patch
(In reply to comment #2) > Created an attachment (id=173776) [details] > Proposed patch Released for 3.6.1 in R3_6_maintenance stream. Kim, could you tag the builder in order to have the perf results generation fixed for next maintenance build? TIA I have generated again the result using the fix and updated performance results HTML pages for M20100630-0800 and M20100707-1005 builds. I have tagged it for the next build. |