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>
For some reason, chell-pre-cq is very flaky (fails in VMTest
login_CryptohomeIncognito for reasons not related to EC changes).
Since pre-submit hook forces us to compile test changes on all platforms
anyway, let's skip chell-pre-cq to unblock developers.
BRANCH=none
BUG=chromium:631640
TEST=chell-pre-cq is not run on EC changes.
Change-Id: I98cb68709bb4305069e5e67874c1847b2a891fb7
Reviewed-on: https://chromium-review.googlesource.com/372618
Reviewed-by: Yoshiki Iguchi <yoshiki@chromium.org>
Commit-Queue: Nicolas Boichat <drinkcat@chromium.org>
Tested-by: Nicolas Boichat <drinkcat@chromium.org>
Right now, firmware changes are rejected if the HWTest or VMTest
stages fail. This is unnecessary as firmware changes are very unlikely
to break these stages.
BUG=chromium:285940
BRANCH=none
TEST=none, this is just copied from the coreboot repository
Change-Id: Id7ccff542b8abada41072ef26cd2b7d3ae179fd3
Signed-off-by: David James <davidjames@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/175410
Reviewed-by: Randall Spangler <rspangler@chromium.org>
