chromeos-base/libchrome fails to emerge
Reported by
jrbarnette@chromium.org,
Jun 24 2016
|
|||||
Issue descriptionAll the canaries are currently red, at least in part because they're unable to build libchrome. Here's the relevant error log output: === Start output for job libchrome-395517-r1 (0m1.0s) === libchrome-395517-r1: >>> Emerging (1 of 1) chromeos-base/libchrome-395517-r1::chromiumos for /build/nyan_kitty/ libchrome-395517-r1: * Running stacked hooks for pre_pkg_setup libchrome-395517-r1: * sysroot_build_bin_dir ... libchrome-395517-r1: [ ok ] libchrome-395517-r1: * Running stacked hooks for pre_src_unpack libchrome-395517-r1: * python_multilib_setup ... libchrome-395517-r1: [ ok ] libchrome-395517-r1: >>> Unpacking source... libchrome-395517-r1: Cloning into '/build/nyan_kitty/tmp/portage/chromeos-base/libchrome-395517-r1/work/libchrome-395517'... libchrome-395517-r1: done. libchrome-395517-r1: fatal: reference is not a tree: 85d6ef31f94c9c39642f0ebc4c1eb08e48edacc1
,
Jun 24 2016
,
Jun 24 2016
The libchrome new commit on 6/23 is https://chromium-review.googlesource.com/#/c/349100/ But the build failure seems from https://chromium-review.googlesource.com/#/c/346457 in whcih set CROS_WORKON_COMMIT="85d6ef31f94c9c39642f0ebc4c1eb08e48edacc1" which lead to ebuild failure
,
Jun 24 2016
This CL is meant to fix it:
https://chromium-review.googlesource.com/#/c/356150/
,
Jun 24 2016
Issue 623112 has been merged into this issue.
,
Jun 24 2016
A local build says that the CL fixed the problem. The canary should turn green with the 18:00 build.
,
Jul 1 2016
Bulk verified |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by jrbarnette@chromium.org
, Jun 24 2016