Love TinderboxPushlog Robot, but on tracking bugs that have a high failure rate on tbpl the robot spams too much. example: https://bugzilla.mozilla.org/show_bug.cgi?id=761987 We should *somehow* figure out if we can fix that.

With treeherder we plan on not using per failure bug notifications. The exact implementation hasn't been decided yet but likely something along the lines of a daily or weekly "this bug has failed N times, 15% of them on opt builds, 20% of the time on android ..." etc.

(In reply to comment #1) > With treeherder we plan on not using per failure bug notifications. The exact > implementation hasn't been decided yet but likely something along the lines of > a daily or weekly "this bug has failed N times, 15% of them on opt builds, 20% > of the time on android ..." etc. What's treeherder? And where would these logs go if not to the bug?

(In reply to :Ehsan Akhgari (needinfo? me!) (slow responsiveness, emailapocalypse) from comment #2) > What's treeherder? And where would these logs go if not to the bug? The replacement for TBPL: http://treeherder.allizom.org/ui/#/jobs https://wiki.mozilla.org/Auto-tools/Projects/Treeherder OrangeFactor will then be made to be a dashboard that uses treeherder-service API, and as such much more robust and useful-for-{job,log}-analysis than the current implementation. Failure analysis can then be performed via the new OrangeFactor, making one to one bug comments to failures unnecessary (I've been getting a lot of grief from the b.m.o admins for the bug spam).

Nice!

Bug 1149783 is filed against Treeherder for this; TBPL is EOL.