Goma failing w/ "reached max number of active fail fallbacks" on the CQ |
||
Issue descriptionhttps://luci-milo.appspot.com/p/chromium/builders/luci.chromium.try/linux_chromium_rel_ng?limit=200 eg: https://luci-milo.appspot.com/p/chromium/builders/luci.chromium.try/linux_chromium_rel_ng/246368 https://luci-milo.appspot.com/p/chromium/builders/luci.chromium.try/linux_chromium_rel_ng/246365 https://luci-milo.appspot.com/p/chromium/builders/luci.chromium.try/linux_chromium_rel_ng/246361 https://luci-milo.appspot.com/p/chromium/builders/luci.chromium.try/linux_chromium_rel_ng/246356 This is starting to happen pretty frequently. ie: for 10-30 minutes at a time every few days, many tryjobs in the middle of compiling crash due to the goma fallback error. (see also bug 908979) Instead of simply waiting it out for the backend to resolve itself, can we instead pursue a more permanent solution? Is there some quota we can indefinitely increase?
,
Dec 3
Never mind, Panopticon wasn't filling in the data before; it doesn't now look like any particular temporal correlation.
,
Dec 3
|
||
►
Sign in to add a comment |
||
Comment 1 by jchinlee@google.com
, Dec 3