Issue metadata
Sign in to add a comment
|
chromiumos-sdk builder is broken |
||||||||||||||||||||||||
Issue descriptionhttps://uberchromegw.corp.google.com/i/chromiumos/builders/chromiumos-sdk/builds/8619 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 based on past experience, seems like a pkg that should be EPI=5 is now using EAPI 6.
,
Mar 23 2018
This is happening often enough that I am considering adding a SDK smoke builder in CQ that will just do cros_sdk --bootstrap.
,
Mar 23 2018
bootstrapping just the SDK (no cross-compilers and no testing boards) still takes ~2hrs. that exceeds any CQ limits currently. jclinton@ has a bigger plan for integrating this more as part of the CI overhaul.
,
Mar 23 2018
,
Mar 23 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/overlays/portage-stable/+/050aea5c38679f6dc21279205f27b5ad44d66a25 commit 050aea5c38679f6dc21279205f27b5ad44d66a25 Author: Manoj Gupta <manojgupta@google.com> Date: Fri Mar 23 01:44:08 2018 pyparsing: Drop to EAPI=5. Fix the SDk builder breakage by changing EAPI to 5. BUG= chromium:825055 TEST=tryjob passed InitSDK stage. Change-Id: I84f17c20f6f686402a9b0079078e4c16dcbb7a6e Reviewed-on: https://chromium-review.googlesource.com/977234 Trybot-Ready: Manoj Gupta <manojgupta@chromium.org> Reviewed-by: Nicolas Boichat <drinkcat@chromium.org> Reviewed-by: Mike Frysinger <vapier@chromium.org> Tested-by: Manoj Gupta <manojgupta@chromium.org> [rename] https://crrev.com/050aea5c38679f6dc21279205f27b5ad44d66a25/dev-python/pyparsing/pyparsing-2.2.0-r1.ebuild |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by manojgupta@chromium.org
, Mar 23 2018