| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Ran the following command:
git grep -l 'Copyright (c)' | \
xargs sed -i 's/Copyright (c)/Copyright/g'
BRANCH=none
BUG=none
TEST=make buildall -j
Change-Id: I6cc4a0f7e8b30d5b5f97d53c031c299f3e164ca7
Signed-off-by: Tom Hughes <tomhughes@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/1663262
Reviewed-by: Daisuke Nojiri <dnojiri@chromium.org>
Reviewed-by: Aseda Aboagye <aaboagye@chromium.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit c7ff23fb5e7057dfda351de004e70b862127a1d0.
Reason for revert: upstream fix[1] is in ToT
[1]https://chromium.googlesource.com/chromiumos/third_party/libqmi/+/a09764425d471c1b5c6c473af55252f4125972c4
Original change's description:
> CQ: disable broken cheza pre-cq
>
> cheza is broken in ToT, removing it from the mandatory pre-CQ configs
> for the EC until it's working again.
>
> BRANCH=None
> BUG=chromium:957280
> TEST=None
>
> Change-Id: I7276ee1a5e7e903d0d0343b3a8b59d88df6ef791
> Signed-off-by: Nicolas Norvez <norvez@chromium.org>
> Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/1586732
> Reviewed-by: Mathew King <mathewk@chromium.org>
> Reviewed-by: Jason Clinton <jclinton@chromium.org>
> Reviewed-by: Sean Abraham <seanabraham@chromium.org>
> Tested-by: Nicolas Boichat <drinkcat@chromium.org>
Bug: chromium:957280
Change-Id: Ib51b50320ea46bea717446b47bb0a78881b59ad6
Reviewed-on: https://chromium-review.googlesource.com/1588296
Commit-Ready: Eric Caruso <ejcaruso@chromium.org>
Tested-by: Eric Caruso <ejcaruso@chromium.org>
Reviewed-by: Eric Caruso <ejcaruso@chromium.org>
Reviewed-by: Sean Abraham <seanabraham@chromium.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
cheza is broken in ToT, removing it from the mandatory pre-CQ configs
for the EC until it's working again.
BRANCH=None
BUG=chromium:957280
TEST=None
Change-Id: I7276ee1a5e7e903d0d0343b3a8b59d88df6ef791
Signed-off-by: Nicolas Norvez <norvez@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/1586732
Reviewed-by: Mathew King <mathewk@chromium.org>
Reviewed-by: Jason Clinton <jclinton@chromium.org>
Reviewed-by: Sean Abraham <seanabraham@chromium.org>
Tested-by: Nicolas Boichat <drinkcat@chromium.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Kevin/Gru are running out of space and we already have another ARM board on
ToT for development. Remove maintenance burden of keeping them around.
BRANCH=none
BUG=chromium:851512
TEST=build_packages --board=kevin works with dependent CLs.
CQ-DEPEND=CL:1102565,CL:*640973,CL:*640974
Change-Id: Ie7c65c7799acc9f4d266e40b29b37240fec345c6
Signed-off-by: Jett Rink <jettrink@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/1100011
Reviewed-by: Ilja H. Friedel <ihf@chromium.org>
Reviewed-by: Randall Spangler <rspangler@chromium.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Because ec is used by the fizz board
BUG=chromium:734783
TEST='cbuildbot --remote fizz-no-vmtest-pre-cq' passes
BRANCH=None
Change-Id: Ib3f7cf5b798e805ed197c79999ff6fc61b07f561
Reviewed-on: https://chromium-review.googlesource.com/540287
Tested-by: Prathmesh Prabhu <pprabhu@chromium.org>
Reviewed-by: Aviv Keshet <akeshet@chromium.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
| |
BRANCH=None
BUG=chromium:692659
TEST=None
Change-Id: I8a7a822cfe57afbfc1d185ae6dfcadc879e342cb
Reviewed-on: https://chromium-review.googlesource.com/443286
Commit-Ready: Ningning Xia <nxia@chromium.org>
Tested-by: Ningning Xia <nxia@chromium.org>
Reviewed-by: Shawn N <shawnn@chromium.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I mistakenly had `chell-no-vmtest-only-pre-cq`, but it turns out that's
not a valid builder config. Just need to drop the "only" part.
BUG=chromium:642503
BRANCH=None
TEST=`cbuildbot --list --all | grep chell-no-vmtest-pre-cq`
Change-Id: I7787eead0c864ba2fe2978bd5679917bef4fa3b2
Signed-off-by: Aseda Aboagye <aaboagye@google.com>
Reviewed-on: https://chromium-review.googlesource.com/383878
Commit-Ready: Aseda Aboagye <aaboagye@chromium.org>
Tested-by: Aseda Aboagye <aaboagye@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Brian Norris <briannorris@chromium.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(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 reverts commit 654271b86c971d7ae32b3f8d798bd1c2c7171f4e.
Apparently ec changes can and do break unit tests on the cq.
BUG=chromium:642503
TEST=None
Change-Id: I88cebf492a4c4a86b75a27ba823a03ffb705a2bb
Reviewed-on: https://chromium-review.googlesource.com/378415
Tested-by: Aviv Keshet <akeshet@chromium.org>
Reviewed-by: Aseda Aboagye <aaboagye@chromium.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Include pre-cq build targets that actually build chromeos-ec.
BUG=chrome-os-partner:56196
BRANCH=None
TEST=Pass pre-cq, verify chosen targets are included.
Change-Id: I175f627c23247bbd269dead8610979118cab8ac7
Signed-off-by: Shawn Nematbakhsh <shawnn@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/368893
Commit-Ready: Douglas Anderson <dianders@chromium.org>
Tested-by: Shawn N <shawnn@chromium.org>
Reviewed-by: Aseda Aboagye <aaboagye@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>
|