COMMIT-QUEUE.ini: Change builders to compile-only.

Really, we only care if the chromeos-ec package fails to build and not
if the test stages fail.  The 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=None
BRANCH=None
TEST=\_()_/

Change-Id: I6a1db02a05f17b276a16543ced58efa8a04fb997
Signed-off-by: Aseda Aboagye <aaboagye@google.com>
Reviewed-on: https://chromium-review.googlesource.com/372325
Commit-Ready: Aseda Aboagye <aaboagye@chromium.org>
Tested-by: Aseda Aboagye <aaboagye@chromium.org>
Reviewed-by: Nicolas Boichat <drinkcat@chromium.org>
This commit is contained in:
Aseda Aboagye
2016-08-18 10:17:15 -07:00
committed by chrome-bot
parent df8289e7f7
commit 654271b86c

View File

@@ -7,8 +7,10 @@
[GENERAL]
# Board-specific pre-cq, include boards that actually build chromeos-ec
pre-cq-configs: gru-pre-cq reef-pre-cq
# Board-specific compile-only-pre-cq, include boards that actually build
# chromeos-ec. We use the compile-only-pre-cq configs since the tests won't
# actually test against our EC changes. (That's what FAFT is for.)
pre-cq-configs: gru-compile-only-pre-cq reef-compile-only-pre-cq chell-compile-only-pre-cq
# Stages to ignore in the commit queue. If these steps break, your CL will be
# submitted anyway. Use with caution.