split remaining mixed-pre-cq builders into single-board configs |
|||||
Issue descriptionFollow up to crbug.com/689224 and a meeting we had. We still get some background rate of BuildPackage/BuildImage/UnitTest failure in the CQ, which could be avoided if we increased the board diversity of the pre-cq. Also, our mixed pre-cq builders don't run BuildImage / UnitTest on all boards (I think). For non-vmtest-running configs, which can run on gce buildslaves, the only limit is our gce fleet, and as far as I know we aren't hitting any limits there. I'll start splitting the mixed configs today (probably 2 at a time) and replacing them with individual [board]-no-vmtest-pre-cq configs. +dgarrett +nxia FYI in the context of gce capacity +sbasi this week's sheriff in case this goes south
,
Feb 10 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/chromite/+/c1624e7d2ab349f18bc5c5d0b245a667974ed0b7 commit c1624e7d2ab349f18bc5c5d0b245a667974ed0b7 Author: Aviv Keshet <akeshet@chromium.org> Date: Fri Feb 10 04:48:49 2017 pre-cq: split out all mixed pre-cq configs mixed-a-pre-cq was the only mixed config that was actually includes multiple boards. Split it into it's consituent boards (and use -no-vmtest rather than -compile-only configs, so that we get BuildImage and UnitTest coverage). For mixed-b and mixed-c, replace them with their solitary board config (again, with -no-vmtest variety rather than -compile-only). BUG= chromium:690527 TEST=Examine config_dump.json, ensure that each of these configs exists. Change-Id: I68e4faf2e733fbf89c44f41905f1b4c3da7b927d Reviewed-on: https://chromium-review.googlesource.com/439815 Commit-Ready: Aviv Keshet <akeshet@chromium.org> Tested-by: Aviv Keshet <akeshet@chromium.org> Reviewed-by: Don Garrett <dgarrett@chromium.org> [modify] https://crrev.com/c1624e7d2ab349f18bc5c5d0b245a667974ed0b7/lib/constants.py
,
Mar 9 2017
,
May 30 2017
,
Aug 1 2017
,
Jan 22 2018
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by aut...@google.com
, Feb 9 2017