Android SoM not showing anything for tree-breaking compile failure |
||||||
Issue description
*all* of the following are red due to compile failures:
chromium.linux:
Android Builder
Android Builder (dbg)
Android Arm64 Builder (dbg)
Android Clang Builder (dbg)
chromium.android
Android {arm,arm64,x64,x86} Builder (dbg)
and *none* of them are showing up in Android SoM. :(
(The chromium.linux ones are showing up in Chromium SoM, though.)
+sheriffs: FYI
,
Mar 14 2017
FYI, it was reverted in r62b8e5996478c00373107e54311dd5966afddd4b Might have something to do with it not going through the CQ?
,
Mar 14 2017
I mean, that's why it landed, but it should still show up in SoM -- and it did for Chromium page on SoM.
,
Mar 14 2017
We determine which builders are tree-breaking by examining the gatekeeper config file: https://chromium.googlesource.com/chromium/tools/build/+/master/scripts/slave/gatekeeper_trees.json#37 <excerpt> "android": { "open-tree": false, "set-status": false, "masters": { "https://build.chromium.org/p/chromium.android": ["*"], "https://build.chromium.org/p/chromium": ["Android"], "https://build.chromium.org/p/chromium.webkit": [ "Android Builder", "Webkit Android (Nexus4)" ], "https://build.chromium.org/p/chromium.linux": [ "Android Builder (dbg)", "Android Tests (dbg)", "Android Builder", "Android Tests", "Android Clang Builder (dbg)", "Cast Android (dbg)" ], "https://build.chromium.org/p/chromium.fyi": [ "Android Builder (dbg)" ] } }, </excerpt> Android Arm64 Builder (dbg) is the only chromium.linux builder that appears to be left out, and anything in chromium.android should be alerted as tree-closing. Looks like we might have a bug in our gatekeeper config logic.
,
May 24 2017
,
Dec 13 2017
Quick update: Looks like we've been alerting on compile failures for most of these builders for a while now: https://bigquery.cloud.google.com/results/sheriff-o-matic:bquijob_42cdeab2_1604d8a502b?pli=1 I don't see any for Clang though.
,
Dec 13
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 18
Is this still a problem?
,
Dec 18
Not sure; we'll refile if it comes back. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by jbudorick@chromium.org
, Mar 14 2017