Opened 7 years ago
Closed 3 years ago
#55883 closed defect (worksforme)
bazel @0.9.0 failed: Worker process sent response with exit code: 1.
Reported by: | ierofant (Андрей Корнилов) | Owned by: | RootFunction |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.4.2 |
Keywords: | Cc: | chrstphrchvz (Christopher Chavez) | |
Port: | bazel |
Description
ERROR: /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_bazel/bazel/work/bazel-0.9.0-dist/src/main/protobuf/BUILD:101:1: Building src/main/protobuf/libcommand_server_java_grpc.jar (1 source jar) failed (Exit 1): java failed: error executing command (cd /opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_bazel/bazel/work/.tmp/bazel_WCtSd3Zd/out/execroot/io_bazel && \ exec env - \ LC_CTYPE=en_US.UTF-8 \ external/local_jdk/bin/java -XX:+TieredCompilation '-XX:TieredStopAtLevel=1' -Xbootclasspath/p:third_party/java/jdk/langtools/javac-9-dev-r4023-3.jar -jar bazel-out/host/bin/src/java_tools/buildjar/java/com/google/devtools/build/buildjar/bootstrap_deploy.jar @bazel-out/darwin-opt/bin/src/main/protobuf/libcommand_server_java_grpc.jar-2.params) java.lang.InternalError: Cannot find requested resource bundle for locale en_US at com.sun.tools.javac.util.JavacMessages.getBundles(JavacMessages.java:128) at com.sun.tools.javac.util.JavacMessages.getLocalizedString(JavacMessages.java:147) at com.sun.tools.javac.util.JavacMessages.getLocalizedString(JavacMessages.java:140) at com.sun.tools.javac.util.Log.localize(Log.java:788) at com.sun.tools.javac.util.Log.printLines(Log.java:586) at com.sun.tools.javac.api.JavacTaskImpl.handleExceptions(JavacTaskImpl.java:170) at com.sun.tools.javac.api.JavacTaskImpl.doCall(JavacTaskImpl.java:96) at com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:90) at com.google.devtools.build.buildjar.javac.BlazeJavacMain.compile(BlazeJavacMain.java:107) at com.google.devtools.build.buildjar.SimpleJavaLibraryBuilder$1.invokeJavac(SimpleJavaLibraryBuilder.java:105) at com.google.devtools.build.buildjar.ReducedClasspathJavaLibraryBuilder.compileSources(ReducedClasspathJavaLibraryBuilder.java:54) at com.google.devtools.build.buildjar.SimpleJavaLibraryBuilder.compileJavaLibrary(SimpleJavaLibraryBuilder.java:108) at com.google.devtools.build.buildjar.SimpleJavaLibraryBuilder.run(SimpleJavaLibraryBuilder.java:116) at com.google.devtools.build.buildjar.BazelJavaBuilder.processRequest(BazelJavaBuilder.java:105) at com.google.devtools.build.buildjar.BazelJavaBuilder.runPersistentWorker(BazelJavaBuilder.java:67) at com.google.devtools.build.buildjar.BazelJavaBuilder.main(BazelJavaBuilder.java:45) Caused by: java.util.MissingResourceException: Can't find bundle for base name com.google.errorprone.errors, locale en_US at java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:1573) at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1396) at java.util.ResourceBundle.getBundle(ResourceBundle.java:854) at com.sun.tools.javac.util.JavacMessages.lambda$add$0(JavacMessages.java:106) at com.sun.tools.javac.util.JavacMessages.getBundles(JavacMessages.java:125) ... 15 more Target //src:bazel failed to build INFO: Elapsed time: 292.793s, Critical Path: 41.21s FAILED: Build did NOT complete successfully ERROR: Could not build Bazel Command failed: ./compile.sh Exit code: 1 Error: Failed to build bazel: command execution failed Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_bazel/bazel/main.log for details.
macOS High Sierra Version 10.13.3
java version "1.8.0_162"
Java(TM) SE Runtime Environment (build 1.8.0_162-b12)
Java HotSpot(TM) 64-Bit Server VM (build 25.162-b12, mixed mode)
Attachments (1)
Change History (12)
Changed 7 years ago by ierofant (Андрей Корнилов)
comment:1 Changed 7 years ago by kencu (Ken)
comment:2 Changed 7 years ago by kencu (Ken)
Oh - looks like you actually have tried bazel 0.90. I see that in the logs but not in the ticket title. I'll fix that.
comment:3 Changed 7 years ago by kencu (Ken)
Cc: | RootFunction added |
---|---|
Port: | bazel added |
Summary: | bazel @0.5.2 failed: Worker process sent response with exit code: 1. → bazel @0.9.0 failed: Worker process sent response with exit code: 1. |
comment:4 Changed 7 years ago by kencu (Ken)
Cc: | RootFunction removed |
---|---|
Owner: | set to RootFunction |
Status: | new → assigned |
comment:5 Changed 7 years ago by RootFunction
Apparently this is a known issue with version 0.90 https://github.com/bazelbuild/bazel/issues/4483. The solution is included in version 0.10 which was recently released. I'll create a PR for this.
comment:6 Changed 7 years ago by RootFunction
This should be resolved by PR 1341 https://github.com/macports/macports-ports/pull/1341 - ierofant, would you give it a try and see if the problem is gone?
comment:7 Changed 7 years ago by ierofant (Андрей Корнилов)
Unfortunately the problem is still reproduced for me.
comment:8 Changed 7 years ago by RootFunction
Would it be possible for you to update and/or re-install the JDK you have? That's the only other possibility I think of.
comment:9 Changed 3 years ago by chrstphrchvz (Christopher Chavez)
This ticket was reported for a relatively ancient version of bazel (0.9.0); the bazel
port is now at 4.1.0, and the oldest version in MacPorts is in the bazel-0.25
port. Can this ticket be closed?
comment:10 Changed 3 years ago by chrstphrchvz (Christopher Chavez)
Cc: | chrstphrchvz added |
---|
comment:11 Changed 3 years ago by reneeotten (Renee Otten)
Resolution: | → worksforme |
---|---|
Status: | assigned → closed |
We updated bazel to 0.90 a short while ago -- please try
sudo port selfupdate
and then try your installation of bazel once again.WARNING - the bazel build can sometimes take a STUPID long time to finish - like 2 to 4 hours - please don't cancel it early. I suggest you run it overnight.
If you know how to fix this, we would all much appreciate the insight. There is info here: <https://github.com/macports/macports-ports/pull/1098>