Create non-tree closing EarlGrey iOS bot, and non-CQ trybot |
||||
Issue descriptionIt would be useful for iOS development to have something other than FYI to monitor iOS EarlGrey tests. These tests aren't ready to be tree closers. We ultimately want to get more things on the CQ, but this would be a short term improvement. Having an optional trybot would be nice for testing iOS patches before landing.
,
Dec 22 2016
,
Dec 22 2016
+dpranke to comment on what's appropriate to be on the main waterfall. My take is that tests don't get to be on the main page unless they're stable, and EG is not there yet. There would be too much red in that column. We should still be able to bring up optional trybots, though? Even if they're not official CQ trybots, there's still a lot of value in letting iOS developers manually send tryjobs to an upstream EG bot. This is basically the same setup we have downstream.
,
Dec 22 2016
Correct, tests should be stable on the non-fyi waterfalls. Test failures don't close the tree these days, but we expect sheriffs to deal with them, so you don't want to create too much work for them. There's no problem with creating optional tryservers that mirror the fyi waterfall builders; we have lots of those.
,
Jun 12 2017
We are in progress of moving EG to the main waterfall and CQ in crbub.com/638141. Trybots have existed for a while on EG. |
||||
►
Sign in to add a comment |
||||
Comment 1 by baxley@chromium.org
, Dec 22 2016