build_image failures in many CQs |
||||
Issue descriptionhttps://luci-milo.appspot.com/buildbot/chromeos/master-paladin/17882 https://luci-milo.appspot.com/buildbot/chromeos/eve-paladin/2502 https://luci-milo.appspot.com/buildbot/chromeos/fizz-paladin/3467 https://luci-milo.appspot.com/buildbot/chromeos/rainier-paladin/583 https://luci-milo.appspot.com/buildbot/chromeos/poppy-paladin/4216 ... pbzip2: *WARNING: Trailing garbage after EOF ignored! emerge: there are no binary packages to satisfy "chromeos-base/trunks" for /mnt/host/source/src/build/images/poppy/R66-10449.0.0-rc2/rootfs/. (dependency required by "virtual/target-chromium-os-1-r86::chromiumos" [binary]) (dependency required by "virtual/target-chrome-os-1-r17::chromeos" [binary]) (dependency required by "virtual/target-os-1.5-r1::chromeos" [binary]) (dependency required by "virtual/target-os" [argument]) Starting fast-emerge. Building package virtual/target-os on /build/poppy Calculating deps... INFO : Unmounting image from /mnt/host/source/src/build/images/poppy/R66-10449.0.0-rc2/stateful and /mnt/host/source/src/build/images/poppy/R66-10449.0.0-rc2/rootfs INFO : Unmounting temporary rootfs /mnt/host/source/src/build/images/poppy/R66-10449.0.0-rc2/rootfs//build/rootfs. Cleaning up /usr/local symlinks for /mnt/host/source/src/build/images/poppy/R66-10449.0.0-rc2/stateful/dev_image An error occurred in your build so your latest output directory is invalid. Running in non-interactive mode so deleting output directory. Deleted /mnt/host/source/src/build/images/poppy/R66-10449.0.0-rc2 [1;31m06:33:51: ERROR: return code: 1; command: /b/c/cbuild/repository/chromite/bin/cros_sdk 'PARALLEL_EMERGE_STATUS_FILE=/tmp/tmpeNF9w0' 'USE=chrome_internal' 'FEATURES=separatedebug' -- ./build_image '--board=poppy' --replace '--version=10449.0.0-rc2' '--builder_path=poppy-paladin/R66-10449.0.0-rc2' base test cmd=['/b/c/cbuild/repository/chromite/bin/cros_sdk', 'PARALLEL_EMERGE_STATUS_FILE=/tmp/tmpeNF9w0', u'USE=chrome_internal', 'FEATURES=separatedebug', '--', './build_image', u'--board=poppy', '--replace', '--version=10449.0.0-rc2', u'--builder_path=poppy-paladin/R66-10449.0.0-rc2', u'base', u'test'], cwd=/b/c/cbuild/repository, extra env={'PARALLEL_EMERGE_STATUS_FILE': '/tmp/tmpeNF9w0', 'USE': u'chrome_internal', 'FEATURES': 'separatedebug'}[0m [1;31m06:33:51: ERROR: ./build_image failed (code=1)[0m
,
Mar 2 2018
There have been no changes to that package in a long time. I don't see why we failed to find the package.
,
Mar 5 2018
nya, I believe you were looking at binary package utilization? This might be interesting to you. With that said, I don't think there's any action items here.
,
Mar 6 2018
+vapier, our portage guru In the log I see: >>> Building file list for packages cleaning... >>> Cleaning binary packages... [ 3.2 M ] /dev-only-extras [ 1.9 G ] chromeos-base/chromeos-chrome-66.0.3357.0_rc-r1 [ 530.7 M ] chromeos-base/chromeos-chrome-66.0.3357.0_rc-r1 [ 2.9 M ] chromeos-base/trunks-0.0.1-r2508 [ 457.6 K ] chromeos-base/trunks-0.0.1-r2508 [ 13.0 K ] Packages Index =========== [ 2.4 G ] Total space from 3 files were freed in the packages directory ... which I guess done at: > "${BOARD_ROOT}/build/bin/eclean" -d packages https://cs.corp.google.com/chromeos_public/src/scripts/build_image?rcl=8e3381b52a943d9da21c8534c0145714989a3186&l=167 How can we prevent eclean from removing the binary package?
,
Mar 7 2018
eclean is supposed to only remove older/unnecessary binpkgs and leave behind current ones. it's interesting that there are duplicates of the binpkgs ... is this failing consistently ?
,
Jun 8 2018
|
||||
►
Sign in to add a comment |
||||
Comment 1 by pprabhu@chromium.org
, Mar 2 2018