BuildPackages stage failed in chromeos-base/chromeos-factory |
|||
Issue descriptionlumpy-incremental-paladin (https://uberchromegw.corp.google.com/i/chromeos/builders/lumpy-incremental-paladin/builds/8409) can't build package: chromeos-factory log: make[1]: Entering directory '/build/lumpy/tmp/portage/chromeos-base/chromeos-factory-0.0.1-r3249/work/chromeos-factory-0.0.1/py/goofy/static' chromeos-factory-0.0.1-r3249: mkdir -p tmp chromeos-factory-0.0.1-r3249: python /opt/closure-library/closure/bin/build/closurebuilder.py --root /opt/closure-library --root ../js -n cros.factory.Goofy -n cros.factory.DeviceManager --compiler_jar=/opt/closure-compiler-bin-0/lib/closure-compiler-bin.jar -f --warning_level=VERBOSE --output_mode=compiled --output_file=/dev/null \ chromeos-factory-0.0.1-r3249: >& tmp/errors.compiled || ( cat tmp/errors.compiled; exit 1 ) chromeos-factory-0.0.1-r3249: cat /opt/closure-library/closure/goog/css/checkbox.css /opt/closure-library/closure/goog/css/common.css /opt/closure-library/closure/goog/css/dialog.css /opt/closure-library/closure/goog/css/menu.css /opt/closure-library/closure/goog/css/menuitem.css /opt/closure-library/closure/goog/css/menuseparator.css /opt/closure-library/closure/goog/css/submenu.css /opt/closure-library/closure/goog/css/tooltip.css /opt/closure-library/closure/goog/css/tree.css | sed -re 's/\/\/ssl\.gstatic\.com\/(closure|editor)/\/images/g' > css/closure.css chromeos-factory-0.0.1-r3249: /opt/closure-library/closure/bin/build/closurebuilder.py: Scanning paths... chromeos-factory-0.0.1-r3249: /opt/closure-library/closure/bin/build/closurebuilder.py: 866 sources scanned. chromeos-factory-0.0.1-r3249: /opt/closure-library/closure/bin/build/closurebuilder.py: Building dependency tree.. chromeos-factory-0.0.1-r3249: Traceback (most recent call last): chromeos-factory-0.0.1-r3249: File "/opt/closure-library/closure/bin/build/closurebuilder.py", line 256, in <module> chromeos-factory-0.0.1-r3249: main() chromeos-factory-0.0.1-r3249: File "/opt/closure-library/closure/bin/build/closurebuilder.py", line 241, in main chromeos-factory-0.0.1-r3249: options.compiler_flags) chromeos-factory-0.0.1-r3249: File "/opt/closure-library/closure/bin/build/jscompiler.py", line 50, in Compile chromeos-factory-0.0.1-r3249: if not (distutils.version.LooseVersion(_GetJavaVersion()) >= chromeos-factory-0.0.1-r3249: File "/opt/closure-library/closure/bin/build/jscompiler.py", line 34, in _GetJavaVersion chromeos-factory-0.0.1-r3249: return _VERSION_REGEX.search(version_line).group(1) chromeos-factory-0.0.1-r3249: AttributeError: 'NoneType' object has no attribute 'group' chromeos-factory-0.0.1-r3249: Makefile:53: recipe for target 'goofy.js' failed chromeos-factory-0.0.1-r3249: make[1]: *** [goofy.js] Error 1 chromeos-factory-0.0.1-r3249: make[1]: Leaving directory '/build/lumpy/tmp/portage/chromeos-base/chromeos-factory-0.0.1-r3249/work/chromeos-factory-0.0.1/py/goofy/static' chromeos-factory-0.0.1-r3249: Makefile:92: recipe for target 'default' failed chromeos-factory-0.0.1-r3249: make: *** [default] Error 2 chromeos-factory-0.0.1-r3249: * ERROR: chromeos-base/chromeos-factory-0.0.1-r3249::chromiumos failed (compile phase): chromeos-factory-0.0.1-r3249: * emake failed It's about infra or chromeos?
,
Sep 8 2016
I'm seeing this on my local build in a completely new checkout. Judging by the error, possibly an unexpressed dependency?
,
Sep 8 2016
my guess is your jre is bjorked. notice the python code is attempting to parse java version output. what does this show on your system inside the sdk ? java -version javac -version here's mine: (cr) $ java -version java version "1.7.0_71" OpenJDK Runtime Environment (IcedTea 2.5.3) (Gentoo package icedtea-7.2.5.3) OpenJDK 64-Bit Server VM (build 24.65-b04, mixed mode) (cr) $ javac -version javac 1.7.0_71
,
Sep 8 2016
Yep, java issue. There's no system VM installed, but closure-library is looking for it: $ java -version basename: missing operand Try 'basename --help' for more information. * Home for VM '' does not exist: * Invalid System VM:
,
Sep 8 2016
So, re-emerge'ing icedtea-bin fixed things: $ sudo emerge icedtea-bin I think it's possible setting up my chroot got interrupted (I had the FS mounted 'nosuid'), so maybe things didn't get setup properly?
,
Sep 9 2016
If #5 is really the likely cause, should we rule out the original report as well, and just close this issue? Or just let it hang around in case someone else hits this again?
,
Sep 9 2016
yes, the jvm is selected during sdk setup. if you killed it partly through, then not a lot we can (or should imo) do about it. otherwise everything that gets run in the sdk setup phase would need to be defensively handled everywhere. the java-config call is the very last thing that gets run today when the sdk is created. that doesn't really explain why the bot failed, and the log is gone. if we can gain more insight, let's reopen. |
|||
►
Sign in to add a comment |
|||
Comment 1 by sosa@google.com
, Apr 6 2016Status: Assigned (was: Untriaged)