Closed
Bug 587812
Opened 14 years ago
Closed 14 years ago
"invalid data, not a float" in tp4 log caused graph server post failure
Categories
(Testing :: Talos, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 595958
People
(Reporter: bhearsum, Unassigned)
Details
In a recent tp4 run (http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1281992509.1281993573.19525.gz) there was an error right at the end of the test:
NOISE: __start_cc_report
NOISE: _x_x_mozilla_cycle_collect,41793
NOISE: __end_cc_report
NOISE: __startTimestamp1281993381726__endTimestamp
NOISE:
NOISE: __startSecondTimestamp1281993382504__endSecondTimestamp
Invalid data, not a float
Completed test tp4:
Stopped Mon, 16 Aug 2010 14:16:34
Which later seems to have caused an error when posting to the Graph Server:
FAIL: Failed to send data 5 times... quitting
RETURN:send failed, graph server says:
RETURN:to determine average from 'test_run_values' for 5073835 - local variable 'values' referenced before assignment
RETURN: File "/data/www/graphs.mozilla.org/server/pyfomatic/collect.py", line 257, in handleRequest
RETURN: average = valuesReader(databaseCursor, databaseModule, inputStream, metadata)
RETURN: File "/data/www/graphs.mozilla.org/server/pyfomatic/collect.py", line 215, in valuesReader
RETURN: raise DatabaseException("to determine average from 'test_run_values' for %s - %s" % (metadata.test_run_id, str(x)))
RETURN:
RETURN:
...which turned the build orange.
Reporter | ||
Comment 1•14 years ago
|
||
Alice, have you ever seen anything like this before?
Reporter | ||
Comment 2•14 years ago
|
||
Actually, I think this probably a bug in Talos itself, should go in the right component.
Component: Release Engineering → Talos
Product: mozilla.org → Testing
QA Contact: release → talos
Version: other → Trunk
Comment 3•14 years ago
|
||
That looks more like a graph server failure...
Reporter | ||
Comment 4•14 years ago
|
||
Looks to me like bad data was sent to the graph server....
These "Invalid data, not a float" are scattered throughout the log. (Also, haven't seen any graph server changes other than data.sql updates in awhile.)
Comment 5•14 years ago
|
||
I think the problem comes for NaNs:
NOISE: _x_x_mozilla_page_load,327.25252525252523,NaN,NaN
Comment 6•14 years ago
|
||
Those NaNs are built into the pageloader report.js:
report += "_x_x_mozilla_page_load,"+avgmed+",NaN,NaN\n"; // max and min are just 0, ignored
Been like that since the beginning.
Comment 7•14 years ago
|
||
hit this today on the 4.0b5 release Linux64 tp4:
http://tinderbox.mozilla.org/showlog.cgi?log=Firefox-Release/1283266348.1283267327.18375.gz
Comment 8•14 years ago
|
||
Patch for this in bug 595958.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•