Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 322766 - [perfs] Performance verification missed a regression introduced after an improvement
Summary: [perfs] Performance verification missed a regression introduced after an impr...
Status: CLOSED INVALID
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Releng (show other bugs)
Version: 3.6   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Frederic Fusier CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 322764
Blocks: 322768
  Show dependency tree
 
Reported: 2010-08-16 05:46 EDT by Frederic Fusier CLA
Modified: 2022-02-03 15:47 EST (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 2010-08-16 05:46:32 EDT 
During the 3.6 dvpt, the performance verification process missed to report a regression because she occurred after that an improvement was made on the test. 

Hence the global results regarding the baseline was flat although it got a severe regression at some point during the dvpt...

The performance tool needs to verify that if an improvement is done at some point, then no regression occurs after this point.
Comment 1 Eclipse Webmaster CLA 2019-09-06 15:30:11 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
Comment 2 Alexander Kurtakov CLA 2022-02-03 15:47:16 EST 
Perf tests need to publish results first in order to see current state and improve after that. 12 years old bugs are not helpful