diff options
author | Brian Norris <briannorris@chromium.org> | 2019-02-28 11:18:48 -0800 |
---|---|---|
committer | chrome-bot <chrome-bot@chromium.org> | 2019-03-01 01:08:38 -0800 |
commit | fc519609fd1fba0e8471dde49236a1af365b1404 (patch) | |
tree | 923b14e1b917b3f8bdb80e3a7df444b6e9a62d44 | |
parent | 90349be2d089d6b85559ee31e744ee864df4b9ed (diff) | |
download | chrome-ec-fc519609fd1fba0e8471dde49236a1af365b1404.tar.gz |
COMMIT-QUEUE: add cheza and flapjack to pre-cq
I've seen these fail a few times in the last few weeks in the CQ. That
shouldn't happen.
BRANCH=none
BUG=none
TEST=none
Change-Id: I7ac16973ee2d11a8e5ea272f20d2ee4d9209b557
Signed-off-by: Brian Norris <briannorris@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1495396
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Reviewed-by: Aseda Aboagye <aaboagye@chromium.org>
-rw-r--r-- | COMMIT-QUEUE.ini | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/COMMIT-QUEUE.ini b/COMMIT-QUEUE.ini index 0dc5447736..948b7fd4eb 100644 --- a/COMMIT-QUEUE.ini +++ b/COMMIT-QUEUE.ini @@ -12,7 +12,8 @@ # actually test against our EC changes. (That's what FAFT is for) pre-cq-configs: kevin-no-vmtest-pre-cq reef-no-vmtest-pre-cq chell-no-vmtest-pre-cq celes-no-vmtest-pre-cq - fizz-no-vmtest-pre-cq + fizz-no-vmtest-pre-cq cheza-no-vmtest-pre-cq + flapjack-no-vmtest-pre-cq # Stages to ignore in the commit queue. If these steps break, your CL will be # submitted anyway. Use with caution. |