summaryrefslogtreecommitdiff
path: root/COMMIT-QUEUE.ini
diff options
context:
space:
mode:
authorBernie Thompson <bhthompson@google.com>2017-06-16 11:34:07 -0700
committerchrome-bot <chrome-bot@chromium.org>2017-06-16 17:24:25 -0700
commitdeeb0ac7de3774b50c8468dfe281e0b9f03d2d46 (patch)
tree1782281a7ddc7c095bb9eebec173d8440bc81367 /COMMIT-QUEUE.ini
parent023a1cb2b3fd4a02bda1ac18783f260323424b8f (diff)
downloadchrome-ec-deeb0ac7de3774b50c8468dfe281e0b9f03d2d46.tar.gz
Use celes-pre-cq instead of strago-pre-cq
The stago build is not well kept after, as it is not used in production, celes however is. BUG=chromium:734103 TEST=None Change-Id: Ie62a4729192fe63d18348f47105a2585c9e4f5be Reviewed-on: https://chromium-review.googlesource.com/538571 Commit-Ready: Bernie Thompson <bhthompson@chromium.org> Tested-by: Bernie Thompson <bhthompson@chromium.org> Reviewed-by: Yixiang Li <yixiang@google.com>
Diffstat (limited to 'COMMIT-QUEUE.ini')
-rw-r--r--COMMIT-QUEUE.ini2
1 files changed, 1 insertions, 1 deletions
diff --git a/COMMIT-QUEUE.ini b/COMMIT-QUEUE.ini
index bbdc357857..55d2459d8d 100644
--- a/COMMIT-QUEUE.ini
+++ b/COMMIT-QUEUE.ini
@@ -11,7 +11,7 @@
# 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-pre-cq
- strago-no-vmtest-pre-cq
+ celes-no-vmtest-pre-cq
# Stages to ignore in the commit queue. If these steps break, your CL will be
# submitted anyway. Use with caution.