Automatically fallback from an equivalent builder |
||
Issue descriptionIf an equivalent builder failed 3 times in a row, fallback to the other builder. This will allow LUCI dogfooders continue their work, but we still would notice the WAIness of LUCI builder because migration app will notice inconsistent results on LUCI and non-LUCI builds on the same patchset. How hard it is to implement? assigning to tandrii to answer this (not necessarily implement)
,
Nov 10 2017
Beta will end in a few weeks when we start converting builders so I think we should only pursue this if the work is very small.
,
Nov 10 2017
> How hard it is to implement? Hard. 2 days for a first crappy version, the decision to fall back won't be remembered across restarts. And CQ code will get worse, I don't like this. But even if this was easy, I don't think I like approach: 0. How do we know 3 failures aren't because CL itself is bad and we aren't just wasting capacity? 1. 3 failed builds is still easily 1-2 hours of delay. 2. 3 failed builds on the same builder is above CQ retry policy, so either we increase retries (which leads to more capacity wasted in Chromium), or we make CQ code even more complex. 3. Suppose this is implemented, what signal do we get from dogfood anyway? If builds are green, devs won't be looking at them anywya. If they are red, there will be fall back to buildbot build. WontFix for now.
,
Nov 10 2017
sg |
||
►
Sign in to add a comment |
||
Comment 1 by no...@chromium.org
, Nov 10 2017