Figure out the cycle time impact to the CQ of building all targets affected by a patch on Mac and Win |
||||
Issue descriptionhttps://codereview.chromium.org/2485473003 landed and caused an outage on the tree due to a compile failure. The target failed to compile on windows, and we didn't catch it because we don't build 'all' in the CQ, intentionally (as explained in bug 665709 ). We should figure out what the impact to the CQ would be if we did compile everything affected by a patch (how many more resources we might need, and what the impact to the cycle time would be), so we can review whether this is still the right tradeoff or not. I believe we currently build 'all' on iOS, Mac, CrOS, and Android, so this would be something to check on Win and Mac.
,
Jun 13 2017
,
Jun 13 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. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 13 2018
I'm tentatively archiving this issue as very old and inactive. If it's still relevant, please reopen and if needed provide an updated request (in particular, do we compile 'all' on Mac, or do we still need to estimate it? - #0 mentions it in both places...) |
||||
►
Sign in to add a comment |
||||
Comment 1 by andyb...@chromium.org
, Jan 18 2017