1079219 - graph server alerts seem way too quiet

Status: RESOLVED FIXED

(Webtools Graveyard :: Graph Server, defect)

Description

[Joel Maher ( :jmaher ) (UTC -8)]

I have seen no regressions from graph server in the last week, but on the flip side Kyle's alerting system has continued to generate alerts.  While we are probably experiencing a break in crazy wild patches, I suspect the analyze_talos.py script is erroring out or failing in some way.

For example look at svg opacity, win8:
http://graphs.mozilla.org/graph.html#tests=%5B%5B225,64,33%5D,%5B225,63,33%5D,%5B225,131,33%5D,%5B225,131,31%5D,%5B225,131,25%5D,%5B225,131,37%5D%5D&sel=none&displayrange=7&datatype=running

on oct 3, we had a bump in the overall number- this was not reported at all on dev.tree-management.

I recall back in May :catlee mentioned having to kick the anaylze_talos.py process due to it hanging or some other error.  We need to look into this now.

Comment 1

[Chris AtLee [:catlee]]

Looks like it's erroring out trying to fetch some revision from pushlog.

Comment 2

[Chris AtLee [:catlee]]

Some data was submitted with revision 0000000NULL, so the regression detector was trying to find when that revision was pushed via:

http://hg.mozilla.org/integration/mozilla-inbound/json-pushes?full=1&changeset=00000000NULL

I've adjusted the script to ignore this kind of failure. Prepare for a flood of alerts!

Comment 3

[Joel Maher ( :jmaher ) (UTC -8)]

alerts are coming out now.  I am not sure why we were sending 000000NULL as the revision, this isn't talos related, but I suspect it is relate to a bug in the browser, maybe related to e10s changes.

shall we close this bug?

Comment 4

[Chris AtLee [:catlee]]

Sure - landed my fixes here - http://hg.mozilla.org/graphs/rev/d6cace45c142