Issue metadata
Sign in to add a comment
|
come up with a better system for prioritizing optional tryjobs |
||||||||||||||||||||||||
Issue descriptionSee bug 842940 for context. Some teams want to build and test additional configurations for some changes to code, and they set up experimental builders on chromium.fyi for those tests and/or optional tryjobs. Those tryjobs can be optionally specified to be included in a CQ job by using the Cq-Include-Trybots footer in the CL description. Currently, because of the way trybot mirroring is done and because of the way chromium.fyi is set up, this can result in some of those optional tryjobs using a lower priority for swarming tasks than tasks on the main waterfall get, and getting starved in the case of an outage. We need a better way of tracking which builders and jobs should have which priorities.
,
May 16 2018
I'm not sure how you define an "optional" trybot but linux_layout_tests_layout_ng is blocking CQ for changes in LayoutNG directories and is affected by this.
,
May 16 2018
Optional in this case is defined as not configured as required in cq.cfg and applied to every CL in the repo regardless of what that CL touches. In this case the bot was added via the Cq-Include-Trybots footer by a presubmit. It would also include trybots where someone added that footer manually.
,
May 22 2018
,
Jun 16 2018
,
Jun 16 2018
haven't actually started this yet ...
,
Oct 6
I'm going to close this as a duplicate of bug 892433, where we're basically now doing this work.
,
Oct 6
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by dpranke@chromium.org
, May 16 2018