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

Issue 857031 link

Starred by 1 user
Status: Duplicate
Merged: issue 854633
Owner: ----
Closed: Jun 2018
Cc:
█ vpalatin@chromium.org
norvez@chromium.org
vapier@chromium.org
haddowk@chromium.org
jclinton@chromium.org
mikenichols@chromium.org
chromeos-continuous-integration-fire-hose@google.com
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 0
Type: Bug



Sign in to add a comment

chromeos-bsp-moblab package build broken

Reported by vpalatin@chromium.org, Jun 27 2018 
The last CQ run failed on :
moblab-generic-vm-paladin: The BuildPackages stage failed: Packages failed in ./build_packages: chromeos-base/chromeos-bsp-moblab in https://luci-milo.appspot.com/buildbot/chromiumos/moblab-generic-vm-paladin/1947

The build failure was :
chromeos-bsp-moblab-0.0.1-r38: fatal: reference is not a tree: 6f63cab36d4f26b6962cd4613ec9ec5e7e8b1335

When looking at the board-overlays repository,
the chromeos-bsp-moblab-0.0.1-r38.ebuild contains :
CROS_WORKON_COMMIT="6f63cab36d4f26b6962cd4613ec9ec5e7e8b1335"
CROS_WORKON_TREE="1985630d1bb4aff083067d7b368dec5a93b25e7f"
CROS_WORKON_PROJECT="chromiumos/overlays/board-overlays"
CROS_WORKON_LOCALNAME="../overlays/"
CROS_WORKON_SUBTREE="project-moblab/chromeos-base/chromeos-bsp-moblab/files"

I don't have a commit 6f63cab36d4f26b6962cd4613ec9ec5e7e8b1335 in my local board-overlays repository either.

The chromeos-bsp-moblab was uprev'ed this morning by :
https://chromium-review.googlesource.com/c/chromiumos/overlays/board-overlays/+/1114388
by this CQ run:
https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8942599561963991040


The particularity of this cros_workon chromeos-bsp-moblab ebuild is that the ebuild is living in the same repository/directory as the one it is working one.
(how does the uprev'ing work in the case, since something else might change the repository in addition to the uprev'ed change ?)

Comment 1 by norvez@chromium.org, Jun 27 2018 

I looked at a few recent uprevs of chromeos-bsp-moblab and I see a pattern:
- if chromeos-bsp-moblab is the only ebuild being uprev'd then CROS_WORKON_COMMIT is set to the correct value
- if another ebuild is uprev'd at the same time (see e.g. commit f940001aa9e625096ef0aed8fa3348efd68758ee) then CROS_WORKON_COMMIT is invalid

Comment 2 by vpalatin@chromium.org, Jun 27 2018

Cc: haddowk@chromium.org mikenichols@chromium.org jclinton@chromium.org
Project Member

Comment 3 by bugdroid1@chromium.org, Jun 27 2018 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/board-overlays/+/52486668978f98d91b1890927b23875b78446399

commit 52486668978f98d91b1890927b23875b78446399
Author: Keith Haddow <haddowk@chromium.org>
Date: Wed Jun 27 13:08:56 2018

[moblab] Remove the trivial change I made last time

The goal is to trigger an uprev to fix the build.

TEST=None
BUG= chromium:857031 

Change-Id: I283d69388f97efaf0243bac410b30fc7c3cfa5be
Reviewed-on: https://chromium-review.googlesource.com/1116866
Reviewed-by: Keith Haddow <haddowk@chromium.org>
Commit-Queue: Keith Haddow <haddowk@chromium.org>
Tested-by: Keith Haddow <haddowk@chromium.org>
Trybot-Ready: Keith Haddow <haddowk@chromium.org>

[modify] https://crrev.com/52486668978f98d91b1890927b23875b78446399/project-moblab/chromeos-base/chromeos-bsp-moblab/chromeos-bsp-moblab-9999.ebuild

Comment 4 by norvez@chromium.org, Jun 27 2018 

The workaround in https://chromium-review.googlesource.com/c/chromiumos/overlays/board-overlays/+/1116866 seems to have worked, chromeos-bsp-moblab has been uprev'd and the new CROS_WORKON_COMMIT points to a valid commit.
To be confirmed in the next CQ run.

Comment 5 by jclinton@chromium.org, Jun 27 2018

Mergedinto: 854633
Status: Duplicate (was: Untriaged)
►

Sign in to add a comment