Re-enable ios-* bots on CQ |
||||
Issue descriptionios-device-xcode-clang does not run by default on cq, but runs on waterfall and can cause CLs to be reverted. This state is highly undesirable because it can cause cases where a CL passes all the try bots get committed only to later break the waterfall and have to be reverted. We should strive to minimize this - so suggest including ios-device-xcode-clang as a default try bot. I think it's especially important in this case because this config uses a different compiler than all the other bots and thus is susceptible to failures that won't affect other build configs. Example case where this happened: https://chromium-review.googlesource.com/c/chromium/src/+/760116
,
Nov 9 2017
We had to pull three of the iOS bots (including this one) off the CQ in July for capacity reasons: https://crbug.com/739556
,
Jan 9 2018
I'm repurposing this bug to bring back all the bots that were made experimental back in July 2017: https://crrev.com/c/582449 The bots in question are ios-device ios-device-xcode-clang ios-simulator-xcode-clang https://chromium.googlesource.com/chromium/src/+/a668b5363cd374a29ca0f46124c226e2e2aa21d9/infra/config/cq.cfg#126 Since this was filed as Pri-3, I'm leaving it as Available, but it should probably be bumped to Pri-2 some time soon.
,
Jan 10
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
,
Jan 10
John, could you take a look at this? |
||||
►
Sign in to add a comment |
||||
Comment 1 by baxley@chromium.org
, Nov 9 2017