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

Issue 903454 link

Starred by 1 user

Issue metadata

Status: Verified
Owner:
Closed: Nov 13
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug
Build-Toolchain



Sign in to add a comment

chromiumos-sdk builder is failing in initsdk stage

Project Member Reported by manojgupta@chromium.org, Nov 8

Issue description

https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8930482704423603136

NFO    cros_sdk:make_chroot: Updating preinstalled build tools
env: ccache: No such file or directory
Traceback (most recent call last):
  File "/mnt/host/source/chromite/bin/parallel_emerge", line 77, in <module>
    from chromite.lib import commandline
  File "/mnt/host/source/chromite/bin/parallel_emerge", line 69, in load_module
    return __import__(mod)
  File "/mnt/host/source/chromite/__init__.py", line 9, in <module>
    import pkg_resources
ImportError: No module named pkg_resources
Running ['/b/swarming/wBHL5LD/ir/cache/cbuild/repository/src/scripts/sdk_lib/make_chroot.sh', '--stage3_path', '/b/swarming/wBHL5LD/ir/cache/cbuild/repository/.cache/sdks/stage3-amd64-2014.09.18.tar.xz', '--chroot', '/b/swarming/wBHL5LD/ir/cache/cbuild/repository/chroot', '--cache_dir', '/b/swarming/wBHL5LD/ir/cache/cbuild/repository/.cache', '--nousepkg'] failed!
13:34:28: ERROR: 
return code: 1; command: /b/swarming/wBHL5LD/ir/cache/cbuild/repository/chromite/bin/cros_sdk --buildbot-log-version --bootstrap --replace '--chrome_root=/b/swarming/wBHL5LD/ir/cache/cbuild/repository/.cache/distfiles/target-master/chrome-src'
cmd=['/b/swarming/wBHL5LD/ir/cache/cbuild/repository/chromite/bin/cros_sdk', '--buildbot-log-version', '--bootstrap', '--replace', '--chrome_root=/b/swarming/wBHL5LD/ir/cache/cbuild/repository/.cache/distfiles/target-master/chrome-src'], cwd=/b/swarming/wBHL5LD/ir/cache/cbuild/repository, extra env={'FEATURES': 'separatedebug', 'CHROME_ORIGIN': 'LOCAL_SOURCE'}



This looks like a common issue where an ebuild that should have EAPI=5 was submitted with EAPI=6.
 
Project Member

Comment 3 by bugdroid1@chromium.org, Nov 8

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/overlays/portage-stable/+/81cc6da8603f92ad9115238fd34a1f5771b96aed

commit 81cc6da8603f92ad9115238fd34a1f5771b96aed
Author: Manoj Gupta <manojgupta@google.com>
Date: Thu Nov 08 20:15:07 2018

dev-python/setuptools: Downgrade EAPI to 5.

Packages needed for portage bootstrap can;t use EAPI=6.

BUG= chromium:903454 
TEST=dev-python/setuptools builds in chromiumos-sdk.

Change-Id: Ic31a437e6a71b1f3832e190c3090112cc2c29b9c
Reviewed-on: https://chromium-review.googlesource.com/c/1327522
Commit-Queue: Manoj Gupta <manojgupta@chromium.org>
Tested-by: Manoj Gupta <manojgupta@chromium.org>
Trybot-Ready: Manoj Gupta <manojgupta@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>

[rename] https://crrev.com/81cc6da8603f92ad9115238fd34a1f5771b96aed/dev-python/setuptools/setuptools-36.7.2-r1.ebuild

I uploaded the guilty CL.

In the future, how can I determine if an ebuild is "needed for portage bootstrap"?
you'd have to run a sdk bot yourself to be fully sure.  otherwise, people use experience.  or wait for Manoj to file bugs ;).
Status: Verified (was: Assigned)

Sign in to add a comment