Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 454923 - fingerprint graphs message about "missing reference" is confusing
Summary: fingerprint graphs message about "missing reference" is confusing
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 12:50 EST by David Williams CLA
Modified: 2020-06-27 20:23 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Williams CLA 2014-12-11 12:50:56 EST
Seems that usually the main "finger print graph" has an asterisk next to each scenario that says or means "missing reference data". 

This is either wrong .. or, I don't understand what it means. 

Or, both. It's obviously not completely missing, since the graphs appear to display current results against reference. So, not sure if they mean "reference data from the latests date that should be available". Or, ... perhaps it means there are scenarios not listed, that should be listed except they are missing reference data ... such as they failed in baseline build? 

Needs investigation as to "what is currently means" and then improve it, so the display and marking of those graphs makes sense to anyone, with no special education.
Comment 1 Dani Megert CLA 2014-12-12 04:16:10 EST
Looking at http://archive.eclipse.org/eclipse/downloads/drops/R-3.7.2-201202080800/performance/performance.php
I can explain some but not all things related to the *.

As we can see on that page:
    Performance of M20120208-0800 relative to R-3.6-201006080911 (201110071800)
the reference performance run (201110071800) is mentioned in the title.

If we look at the data of the fingerprints below that don't have a *, we see  that 201110071800 was indeed used as the reference build, e.g.
http://archive.eclipse.org/eclipse/downloads/drops/R-3.7.2-201202080800/performance/eplnx1/Scenario483.html


If we look at the data of the fingerprints below that do have a *, we see  that 201110071800 was NOT used as the reference build. An older one was used, e.g.
http://archive.eclipse.org/eclipse/downloads/drops/R-3.7.2-201202080800/performance/epwin2/Scenario483.html

The fingerprints with a star also have the reference build that was used instead of the main/master reference build in their name in brackets.


What I cannot explain is why those with a * did not use the correct (the one in the title) reference build. First I thought maybe the (last) reference build for that platform failed, but if we look at the fingerprints we see that both are for the same platform (assuming the header was correct back then):
    Win XP Sun 1.6.0_17 (2 x 3.00GHz - 3GB RAM)
Maybe this was done on purpose i.e. run against the latest and an older reference build to see whether there's difference / trend. This could give a hint about the stability of the different reference builds.

HTH a bit.
Comment 2 Eclipse Genie CLA 2020-06-27 20:23:23 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.

--
The automated Eclipse Genie.