Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 290163

Summary: [results] performance reports make specific assumptions about qualifier and baseline format
Product: [Eclipse Project] Platform Reporter: Steffen Pingel <steffen.pingel>
Component: RelengAssignee: Frederic Fusier <frederic_fusier>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: P3 CC: david_williams, kim.moir, psuzzi
Version: 3.6   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard:

Description Steffen Pingel CLA 2009-09-22 14:14:28 EDT 
While setting up performance reporting for Mylyn I noticed that the report generator requires certain input formats to correctly recognize baselines and to parse dates. If these conventions are not followed report generation fails with exceptions (e.g. in Util.getBuildDate()) or see DB_Results.DEFAULT_DB_BASELINE_PREFIX).

The performance reporting is a very useful tool and it would be great if it was reusable by other projects. I think it's reasonable to require these conventions but it would be helpful for consumers if reporting failed with meaningful exceptions when conventions are not followed.
Comment 1 David Williams CLA 2016-01-26 20:31:17 EST 
While this is a very old bug, I am seeing similar things even now, so will mark this as a dup of "current" bug. I can't promise to fix all "hard coded assumptions" ... but hope to make it better.

*** This bug has been marked as a duplicate of bug 481272 ***