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

Issue 736389 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner: ----
Closed: Jun 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

reef-uni builder failed on SignerTest

Project Member Reported by yueherngl@chromium.org, Jun 23 2017

Issue description

reef-uni build is finally online but with builder error on SignerTest.

https://uberchromegw.corp.google.com/i/chromeos/builders/reef-uni-release/builds/1

Looking further, the failure is 

ensure_sane_lsb-release.sh: INFO   : Loading config from /mnt/host/source/cros-signing/security_test_baselines/ensure_sane_lsb-release.config
ensure_sane_lsb-release.sh: ERROR  : CHROMEOS_RELEASE_BOARD: Value 'reef-uni' was not recognized
ensure_sane_lsb-release.sh: ERROR  : Unknown board: reef-uni

As this checks the appid, do we need to add a dummy appid for it (as an appid seems to be defined under GE)?

Thanks.

 
Not sure if this is right approach,

https://chrome-internal-review.googlesource.com/#/c/400528/

adds the check (where the appid defined in GE).

But I don't find anywhere that we are adding appid (e.g. doappid) for reef-uni?
Cc: pbe...@chromium.org nsanders@chromium.org
RE: #1

Perhaps with this? https://chrome-internal-review.googlesource.com/#/c/401090/
I know this works with typical setup... not sure about reef-uni, though.
Thanks.

Status: Fixed (was: Untriaged)
Mark it fixed. VM test failure being tracked by separate bug.

https://b.corp.google.com/issues/63011532

Please re-open or file new bug if in need.

Thanks.

Sign in to add a comment