CQ lacks coverage for Android builds w/ symbol_level = 1 |
|||||||
Issue descriptionCQ lacks coverage for Android builds w/ symbol_level = 1 I had the CQ land a CL for me that broke the main waterfall. The builders that broke had "symbol_level = 1" in their GN config. Apparently, none of the CQ bots have this config. For reference, here's the buildbot that failed: https://build.chromium.org/p/chromium/builders/Android/builds/61265/ Here's the offending CL: https://codereview.chromium.org/2224713002
,
Sep 1 2016
,
Sep 13 2016
Stip - is this build config considered as part of adding Android builds to the Chromium CQ that was being discussed yesterday? If not, Paweł - do we have objective criteria for adding additional build configs to the CQ or at least proposing them for chrome-eng-leads to review?
,
Sep 13 2016
We have cycle time goals, then there's capacity and success rate. I think chrome-eng-review's decision is critical. Once we decide to move forward we can make things happen.
,
Feb 10 2017
,
Mar 9 2018
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. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 9 2018
linux_android_rel_ng builds w/ symbol_level=1 at this point. Not sure when that changed between 8/2016 and now. |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by tandrii@chromium.org
, Aug 29 2016Components: -Infra>CQ Infra>Client>Chrome