Closed
Bug 1174160
Opened 9 years ago
Closed 9 years ago
windows 8 fails to collect tp5 responsiveness a lot of the time
Categories
(Testing :: Talos, defect)
Testing
Talos
Tracking
(e10s+, firefox41 affected)
RESOLVED
FIXED
People
(Reporter: jmaher, Unassigned)
Details
most of the errors in bug 1124697 are related to not collecting the responsiveness metric, mostly on windows 8.
we should figure this out as this metric is good for tracking chrome performance now that e10s is becoming a reality.
Comment 1•9 years ago
|
||
This doesn't sound like a problem with the individual test -
07:04:24 CRITICAL - FAIL: Graph server unreachable (5 attempts)
07:04:24 INFO - RETURN:send failed, graph server says:
07:04:24 INFO - RETURN:No test_name called 'tp5o' can be found
07:04:24 INFO - RETURN: File "/var/www/html/graphs/server/pyfomatic/collect.py", line 293, in handleRequest
07:04:24 INFO - RETURN: metadata = MetaDataFromTalos(databaseCursor, databaseModule, inputStream)
07:04:24 INFO - RETURN: File "/var/www/html/graphs/server/pyfomatic/collect.py", line 63, in __init__
07:04:24 INFO - RETURN: self.doDatabaseThings(databaseCursor)
07:04:24 INFO - RETURN: File "/var/www/html/graphs/server/pyfomatic/collect.py", line 106, in doDatabaseThings
07:04:24 INFO - RETURN: raise DatabaseException("No test_name called '%s' can be found" % self.test_name)
07:04:24 INFO - RETURN:
07:04:24 INFO - RETURN:
Updated•9 years ago
|
tracking-e10s:
--- → ?
Reporter | ||
Comment 2•9 years ago
|
||
that is the error when we have no data for a specific counter, in this case tp5 responsiveness. Yes, I agree, it isn't a pretty error.
Updated•9 years ago
|
Reporter | ||
Comment 4•9 years ago
|
||
lets mark this as resolved and reopen if this is a repeated trend.
Status: NEW → RESOLVED
Closed: 9 years ago
Flags: needinfo?(jmaher)
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•