SetupBoard failure in tricky-tot-chrome-pfq-informational |
|||
Issue descriptionFirst 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'
,
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
,
Jun 23 2016
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.
,
Jun 23 2016
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?
,
Jun 23 2016
Next build is green :) Closing as WontFix due to the issue having resolved on itself.
,
Jun 24 2016
Issue 623115 has been merged into this issue. |
|||
►
Sign in to add a comment |
|||
Comment 1 by h...@chromium.org
, Jun 23 2016Owner: lhchavez@chromium.org
Status: Assigned (was: Untriaged)