Bug 201564 - [results] Problem in performance results generation since 3.3 maintenance
Summary: [results] Problem in performance results generation since 3.3 maintenance
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Releng (show other bugs)
Version: 3.3   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: 3.5 M3   Edit
Assignee: Frederic Fusier CLA
QA Contact:
URL:
Whiteboard:
Keywords: performance, test
Depends on:
Blocks:
 
Reported: 2007-08-29 09:40 EDT by Frederic Fusier CLA
Modified: 2008-09-19 04:41 EDT (History)
1 user (show)

See Also:

Attachments
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 CLA 2007-08-29 09:40:22 EDT 
Looking at performance results for maintenance builds, I saw different issues since the maintenance stream has started:

1) History table in 'Raw data and Stats' html page does not have any maintenance build results (eg. M2007xxxx-yyyy build)
2) History graphs for scenario show results for integration builds since July 2007 but also results for nightly builds!
Comment 1 Frederic Fusier CLA 2007-08-29 09:42:51 EDT 
Kim, I think the first issue and nightly builds should be solved if you change the -currentPrefix parameter value from 'N,I' to 'I,M'.

I'll investigate why the integration builds can be added since end of June in these graphs and how to fix it...
Comment 2 Kim Moir CLA 2007-09-10 16:24:02 EDT 
Released fix to 3.3 maintenance stream and tagged for next build.

Note this paramater is excluded by default and has to be added to m-stream builders, otherwise the default is N,I
Comment 3 Kim Moir CLA 2007-10-12 10:27:43 EDT 
Still doesn't seem to be generating the data for the M builds
Comment 4 Frederic Fusier CLA 2007-10-15 07:07:21 EDT 
Would it be possible to copy the perfDB content on JDT/Core drive to help me to debug with local data and have a chance to understand what happen there?
TIA
Comment 5 Kim Moir CLA 2007-10-15 08:56:30 EDT 
Yes, I'll copy them over once last night's performance tests are complete and I can shutdown the database.
Comment 6 Frederic Fusier CLA 2008-09-18 12:08:43 EDT 
The parameter name was 'current.prefix' instead of currentPrefix... :-(
I've modified the generator to avoid to have to set it explicitely. Now, when the build ID starts with 'M', the build prefixes used are by default 'I' and 'M' instead of 'I' and 'N'...

Consider this issue is fixed in HEAD.