Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 454929 - Line graphs (and others statistics) should show each 'baseline' datapoint
Summary: Line graphs (and others statistics) should show each 'baseline' datapoint
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Releng (show other bugs)
Version: 4.5   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Releng-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks: 454921
  Show dependency tree
 
Reported: 2014-12-11 13:39 EST by David Williams CLA
Modified: 2019-11-27 06:58 EST (History)
0 users

See Also:

Attachments
example image from URL, since URL will be removed soon. (5.37 KB, image/gif)
2014-12-11 13:41 EST, David Williams CLA 		no flags Details
View All 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 David Williams CLA 2014-12-11 13:39:52 EST 
Especially in line graphs, such as at 

http://download.eclipse.org/eclipse/downloads/drops4/I20141210-0800/performance/linux.gtk.x86_64/Scenario1.html

we really should display *each* baseline data point that "goes with" the I-build ... since we do, after all, run the base line for each build. I think the performance ui program currently simply takes "most recent run".
Comment 1 David Williams CLA 2014-12-11 13:41:07 EST 
Created attachment 249362 [details]
example image from URL, since URL will be removed soon.
Comment 2 Lars Vogel CLA 2019-11-27 06:58:02 EST 
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.

If the bug is still relevant, please remove the stalebug whiteboard tag.