Closed Bug 510048 Opened 15 years ago Closed 15 years ago

Graph server shows wrong changeset ids

Categories

(Release Engineering :: General, defect, P1)

x86
macOS
defect

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 500194

People

(Reporter: jrmuizel, Unassigned)

Details

When I load the following the following:

http://graphs.mozilla.org/graph.html#tests=[{%22machine%22:55,%22test%22:18,%22branch%22:1},{%22machine%22:56,%22test%22:18,%22branch%22:1},{%22machine%22:57,%22test%22:18,%22branch%22:1},{%22machine%22:71,%22test%22:18,%22branch%22:1},{%22machine%22:108,%22test%22:18,%22branch%22:1},{%22machine%22:109,%22test%22:18,%22branch%22:1},{%22machine%22:110,%22test%22:18,%22branch%22:1},{%22machine%22:111,%22test%22:18,%22branch%22:1},{%22machine%22:112,%22test%22:18,%22branch%22:1},{%22machine%22:113,%22test%22:18,%22branch%22:1},{%22machine%22:114,%22test%22:18,%22branch%22:1},{%22machine%22:115,%22test%22:18,%22branch%22:1},{%22machine%22:116,%22test%22:18,%22branch%22:1},{%22machine%22:117,%22test%22:18,%22branch%22:1},{%22machine%22:118,%22test%22:18,%22branch%22:1},{%22machine%22:119,%22test%22:18,%22branch%22:1},{%22machine%22:120,%22test%22:18,%22branch%22:1},{%22machine%22:121,%22test%22:18,%22branch%22:1},{%22machine%22:122,%22test%22:18,%22branch%22:1},{%22machine%22:123,%22test%22:18,%22branch%22:1},{%22machine%22:124,%22test%22:18,%22branch%22:1},{%22machine%22:125,%22test%22:18,%22branch%22:1},{%22machine%22:126,%22test%22:18,%22branch%22:1}]&sel=1249991940,1250164740

I get the following value for the latest point on the talos-rev2-xp03 machine:

Date: 8/12/2009 9:40 AM Value: 1041.18 Changeset: d9d6c835c2df

The changeset id is wrong and should be: ca46dd208b99.

As shown here:
http://graphs.mozilla.org/graph.html#tests=[{%22test%22:%2218%22,%22branch%22:%221%22,%22machine%22:%22110%22}]&sel=1249991940,1250164740

There are other points that have the wrong changesets as well.

The query results from the server are still correct even when the values are displayed wrong so the bug is in the js code someplace.
We looked into it a bit, and it looks like the response from the server has the correct changeset, as jeff said, but the extra_data value that's set on the dataset has an incorrect value.  In the mouse move handler, finding the closest point seems to succeed, and the right indices for dataset/index are used for getting the time and the value, so the wrong thing is in the extra_data array.
Possible dupe of bug 500194 ?
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → DUPLICATE
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.