Use separate pools for LUCI tasks of WebRTC between CI and TRY |
|||
Issue descriptionBackground: https://groups.google.com/a/google.com/d/msg/luci-eng/n62bxU_rAJs/KRgnA8vnAAAJ tl;dr for recipe-running tasks executed on swarming, there must be a separation between try and CI (or cron) jobs. Today, you have just 1 pool WebRTC.LUCI: https://chromium-swarm.appspot.com/botlist?c=id&c=os&c=task&c=status&c=pool&f=pool%3AWebRTC.LUCI&l=100&s=id%3Aasc Please: 1. only put CI tasks into your current WebRTC.LUCI pool. 2. create a try pool, perhaps WebRTC.LUCI.Try, for tryjobs. Note, this isn't about running isolated tests (yet, perhaps).
,
Oct 25 2017
Edward has all LUCI migration bugs for now.
,
Oct 27 2017
The following revision refers to this bug: https://chrome-internal.googlesource.com/infradata/config/+/849a7ffc986b72116ac87dd1b52cde60dc41b07c commit 849a7ffc986b72116ac87dd1b52cde60dc41b07c Author: Edward Lemur <ehmaldonado@google.com> Date: Fri Oct 27 09:23:02 2017
,
Jan 24 2018
|
|||
►
Sign in to add a comment |
|||
Comment 1 by anatolid@chromium.org
, Oct 25 2017