From 64d6f5781becdf43b8de29a242277bc98b3b4b1e Mon Sep 17 00:00:00 2001 From: Aseda Aboagye Date: Tue, 6 Sep 2016 10:06:03 -0700 Subject: [PATCH] COMMIT-QUEUE.ini: Change builders to no-vmtest-pre-cq. (Re-attempt of https://chromium-review.googlesource.com/#/c/372325/) Really, we only care if the chromeos-ec package unit tests fail and not if the VMTest or ImageTest stages fail. Those test stages don't actually test aganist our EC changes anways, so it's kind of a waste of time to run them. Besides, that's what FAFT is for. BUG=chromium:642503 BRANCH=None TEST=cbuildbot --remote chell-no-vmtest-pre-cq Change-Id: I1b4b7fc68a9f8a943f6f5ef3d8b169264c95359e Signed-off-by: Aseda Aboagye Reviewed-on: https://chromium-review.googlesource.com/381106 Commit-Ready: Aseda Aboagye Tested-by: Aseda Aboagye Reviewed-by: Bernie Thompson Reviewed-by: Mike Frysinger --- COMMIT-QUEUE.ini | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/COMMIT-QUEUE.ini b/COMMIT-QUEUE.ini index 64538e763a..6f0a858f0c 100644 --- a/COMMIT-QUEUE.ini +++ b/COMMIT-QUEUE.ini @@ -7,9 +7,11 @@ [GENERAL] -# Board-specific pre-cq, include boards that actually build chromeos-ec -pre-cq-configs: gru-pre-cq reef-pre-cq +# Board-specific no-vmtest-pre-cq, include boards that actually build +# chromeos-ec. We use the no-vmtest-pre-cq configs since the tests won't +# actually test against our EC changes. (That's what FAFT is for) +pre-cq-configs: gru-no-vmtest-pre-cq reef-no-vmtest-pre-cq chell-no-vmtest-only-pre-cq # Stages to ignore in the commit queue. If these steps break, your CL will be # submitted anyway. Use with caution. -ignored-stages: HWTest VMTest +ignored-stages: HWTest ImageTest VMTest