New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 621993 link

Starred by 2 users

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: Jun 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

cros-ec: Build is broken due to non-existing private folder

Project Member Reported by sha...@chromium.org, Jun 21 2016

Issue description

This patch added a dependency on a private folder from within a public board:

https://chromium-review.googlesource.com/347462

Currently public committers can't pass pre-commit checks. Shall we add cr50 to 'skip_boards' so that it's not built as part of `make buildall`?

 
what is the actual problem?

https://chromium-review.googlesource.com/350095 was meant to exclude cr50 from buildall when building on the bot. 

Comment 2 by sha...@chromium.org, Jun 21 2016

cros-ec has public contributors that aren't bots :)

make[2]: *** No rule to make target 'private-cr51/build.mk'.  Stop.
Makefile.rules:115: recipe for target 'proj-cr50' failed
make[1]: *** [proj-cr50] Error 2
make[1]: *** Waiting for unfinished jobs....

It's related to this line that was added to board/cr50/build.mk:

# Add hardware crypto support.
PDIR=private-cr51
well, I am not sure what is the best way to do it then - I would rather not exclude cr50 from makeall unconditionally.

Can the public contributors be educated to remove cr50 directory before running makeall?

Comment 4 by sha...@chromium.org, Jun 21 2016

> Can the public contributors be educated to remove cr50 directory before running makeall?

Yes, but it's an inconvenience, and it seems like a generally unfriendly thing to do, if we take cros-ec seriously as an open source project.

Can cr50 be made entirely private, or can it be reworked to still build even if private-cr51 is absent?
In fact there are plans of making cr50 entirely public.

Permanently excluding it from makeall is not a good idea as this would let build breakages creep in.

Comment 6 by sha...@chromium.org, Jun 21 2016

Let's land https://chromium-review.googlesource.com/#/c/354540/ (or similar) which will exclude cr50 from `make buildall` when private-cr51 is not present. Then, we can revert https://chromium-review.googlesource.com/350095 and correctly fail in case cr50 adds more private dependencies later.
Project Member

Comment 7 by bugdroid1@chromium.org, Jun 22 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform/ec/+/58c0727901aae21c496056a5eccaa27c693510ef

commit 58c0727901aae21c496056a5eccaa27c693510ef
Author: Shawn Nematbakhsh <shawnn@chromium.org>
Date: Tue Jun 21 19:37:01 2016

build: Skip cr50 board in `make buildall` if private folder not present

BUG= chromium:621993 
BRANCH=None
TEST=`make buildall -j` from public checkout succeeds. Also verify cr50
still built from private checkout.

Change-Id: I982806e282146aab76154b51c366226d3d1aed14
Signed-off-by: Shawn Nematbakhsh <shawnn@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/354540
Commit-Ready: Shawn N <shawnn@chromium.org>
Tested-by: Shawn N <shawnn@chromium.org>
Reviewed-by: Vadim Bendebury <vbendeb@chromium.org>

[modify] https://crrev.com/58c0727901aae21c496056a5eccaa27c693510ef/Makefile.rules

Project Member

Comment 8 by bugdroid1@chromium.org, Jun 22 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/chromiumos-overlay/+/95147e4c4d36c69f5bd61fb548b429712ec71052

commit 95147e4c4d36c69f5bd61fb548b429712ec71052
Author: Shawn N <shawnn@chromium.org>
Date: Wed Jun 22 01:39:58 2016

Revert "chromeos-ec: do not build cr50 when making buildall"

CL:354540 skips building cr50 when dependent private folders are not
present, so this ebuild modification should no longer be necessary to
pass `make buildall` on public builders.

BUG= chromium:621993 
BRANCH=None
TEST=`emerge-glados chromeos-ec` from public checkout,
verify no failure.

Change-Id: Ic7a5dba5a6f447639dcd1a58b0e640d31f03d5a4
Reviewed-on: https://chromium-review.googlesource.com/354771
Commit-Ready: Shawn N <shawnn@chromium.org>
Tested-by: Shawn N <shawnn@chromium.org>
Reviewed-by: Vadim Bendebury <vbendeb@chromium.org>

[modify] https://crrev.com/95147e4c4d36c69f5bd61fb548b429712ec71052/chromeos-base/chromeos-ec/chromeos-ec-9999.ebuild

Comment 9 by sha...@chromium.org, Jun 22 2016

Cc: -sha...@chromium.org ngm@chromium.org
Owner: sha...@chromium.org
Status: Fixed (was: Untriaged)
Status: Verified (was: Fixed)
Bulk verified

Sign in to add a comment