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 <aaboagye@google.com>
Reviewed-on: https://chromium-review.googlesource.com/381106
Commit-Ready: Aseda Aboagye <aaboagye@chromium.org>
Tested-by: Aseda Aboagye <aaboagye@chromium.org>
Reviewed-by: Bernie Thompson <bhthompson@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
This commit is contained in:
Aseda Aboagye
2016-09-06 10:06:03 -07:00
committed by chrome-bot
parent 30f978d9c1
commit 64d6f5781b

View File

@@ -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