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

Issue 622790 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner:
Last visit 16 days ago
Closed: Jun 2016
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

SetupBoard failure in tricky-tot-chrome-pfq-informational

Project Member Reported by h...@chromium.org, Jun 23 2016

Issue description

First failure in https://uberchromegw.corp.google.com/i/chromeos.chrome/builders/tricky-tot-chrome-pfq-informational/builds/1231/

libchrome-395517-r1: Cloning into '/var/tmp/portage/chromeos-base/libchrome-395517-r1/work/libchrome-395517'...
libchrome-395517-r1: done.
libchrome-395517-r1: fatal: reference is not a tree: 85d6ef31f94c9c39642f0ebc4c1eb08e48edacc1
libchrome-395517-r1:  * ERROR: chromeos-base/libchrome-395517-r1::chromiumos failed (unpack phase):
libchrome-395517-r1:  *   git-2_branch: changing the branch failed
libchrome-395517-r1:  * 
libchrome-395517-r1:  * Call stack:
libchrome-395517-r1:  *     ebuild.sh, line   93:  Called src_unpack
libchrome-395517-r1:  *   environment, line 3332:  Called cros-workon_src_unpack
libchrome-395517-r1:  *   environment, line  826:  Called git-2_src_unpack
libchrome-395517-r1:  *   environment, line 2208:  Called git-2_branch
libchrome-395517-r1:  *   environment, line 1993:  Called die
libchrome-395517-r1:  * The specific snippet of code:
libchrome-395517-r1:  *       git checkout -b ${branchname} ${src} || die "${FUNCNAME}: changing the branch failed";
libchrome-395517-r1:  * 
libchrome-395517-r1:  * If you need support, post the output of `emerge --info '=chromeos-base/libchrome-395517-r1::chromiumos'`,
libchrome-395517-r1:  * the complete build log and the output of `emerge -pqv '=chromeos-base/libchrome-395517-r1::chromiumos'`.
libchrome-395517-r1:  * The complete build log is located at '/var/log/portage/chromeos-base:libchrome-395517-r1:20160623-175029.log'.
libchrome-395517-r1:  * For convenience, a symlink to the build log is located at '/var/tmp/portage/chromeos-base/libchrome-395517-r1/temp/build.log'.
libchrome-395517-r1:  * The ebuild environment file is located at '/var/tmp/portage/chromeos-base/libchrome-395517-r1/temp/environment'.
libchrome-395517-r1:  * Working directory: '/var/tmp/portage/chromeos-base/libchrome-395517-r1/work/libchrome-395517'
libchrome-395517-r1:  * S: '/var/tmp/portage/chromeos-base/libchrome-395517-r1/work/libchrome-395517'
libchrome-395517-r1: >>> Failed to emerge chromeos-base/libchrome-395517-r1, Log file:
libchrome-395517-r1: >>>  '/var/log/portage/chromeos-base:libchrome-395517-r1:20160623-175029.log'
 

Comment 1 by h...@chromium.org, Jun 23 2016

Cc: henryhsu@chromium.org
Owner: lhchavez@chromium.org
Status: Assigned (was: Untriaged)
+ lhchavez@ and CC henryhsu@

The "fatal: reference is not a tree: 85d6ef31f94c9c39642f0ebc4c1eb08e48edacc1" points to your CL https://chromium-review.googlesource.com/#/c/349100/ which appears to be already merged.

Can you take a look if this is a one-off thing due to the nature of updating libchrome?

Comment 2 by ihf@chromium.org, Jun 23 2016

It may be cycling green, as the next build is going past setup_board
https://uberchromegw.corp.google.com/i/chromeos.chrome/builders/tricky-tot-chrome-pfq-informational/builds/1232
It does look transient. The second attempt's error log (in the failed build) look different. At least it already had all objects downloaded. I'll keep an eye on it.
Oh actually, the next build has a few changes that should have gone in the previous one:

https://chrome-internal-review.googlesource.com/#/c/260878/
https://chromium-review.googlesource.com/#/c/349001/

is that normal/expected? There was a very large amount of dependent CLs, did we miss a dependency?
Status: WontFix (was: Assigned)
Next build is green :) Closing as WontFix due to the issue having resolved on itself.

Comment 6 by h...@chromium.org, Jun 24 2016

Cc: reinauer@chromium.org zhihongyu@chromium.org keta...@chromium.org amstan@chromium.org joth@chromium.org
 Issue 623115  has been merged into this issue.

Sign in to add a comment