Sheriff-o-Matic doesn't report compile failure from Win x64 GN (dbg) |
|||||
Issue descriptionProblem with Sheriff-o-Matic: https://sheriff-o-matic.appspot.com/chromium While I was serving as build sheriff, there was a compile failure on "Win x64 GN (dbg)", but that didn't get reported to sheriff-o-matic at all, even three failed builds later: https://build.chromium.org/p/chromium.win/builders/Win%20x64%20GN%20%28dbg%29/builds/19428 I eventually noticed it while looking at the waterfall and reverted the culprit CL, but it'd be nice to get the notice from sheriff-o-matic, as that's what I was using for my primary monitoring. I'm not sure if this bot is considered less important or special in some way, since it also (surprisingly) didn't close the tree.
,
Mar 11 2016
@alexmos - those bots intentionally don't close the tree, because they do not have matching bots on the CQ. See bug 486089 . I do have a patch outstanding to get these failures going into sheriff-o-matic *even though* they currently don't close the tree: https://codereview.chromium.org/1703353002/ The reason they're not in SoM now is *because* they also don't close the tree :(.
,
Mar 11 2016
Not sure what a trooper is supposed to do for this bug
,
Mar 11 2016
@nodir - there's nothing for you to do, I don't think ...
,
Apr 5 2016
,
Apr 27 2016
,
Jun 9 2016
Dirk's CL has landed, so these should show up in SoM now. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by alex...@chromium.org
, Mar 11 2016