<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"><html><head><meta content="text/html;charset=UTF-8" http-equiv="Content-Type"></head><body ><div style='font-size:10pt;font-family:Verdana,Arial,Helvetica,sans-serif;'><div>When the Bazel port was committed, a number of build jobs failed. A link to each one is listed below.<br></div><div><br></div><div><a href="https://build.macports.org/builders/ports-10.8_x86_64_legacy-watcher/builds/7383">https://build.macports.org/builders/ports-10.8_x86_64_legacy-watcher/builds/7383</a><br></div><div><a href="https://build.macports.org/builders/ports-10.10_x86_64-watcher/builds/7380">https://build.macports.org/builders/ports-10.10_x86_64-watcher/builds/7380</a><br></div><div><a href="https://build.macports.org/builders/ports-10.9_x86_64-watcher/builds/7386">https://build.macports.org/builders/ports-10.9_x86_64-watcher/builds/7386</a><br></div><div><a href="https://build.macports.org/builders/ports-10.7_x86_64_legacy-watcher/builds/7414">https://build.macports.org/builders/ports-10.7_x86_64_legacy-watcher/builds/7414</a><br></div><div><a href="https://build.macports.org/builders/ports-10.11_x86_64-watcher/builds/7381">https://build.macports.org/builders/ports-10.11_x86_64-watcher/builds/7381</a><br></div><div><a href="https://build.macports.org/builders/ports-10.12_x86_64-watcher/builds/6290">https://build.macports.org/builders/ports-10.12_x86_64-watcher/builds/6290</a><br></div><div><a href="https://build.macports.org/builders/ports-10.6_x86_64_legacy-watcher/builds/7376">https://build.macports.org/builders/ports-10.6_x86_64_legacy-watcher/builds/7376</a><br></div><div><a href="https://build.macports.org/builders/ports-10.6_i386_legacy-watcher/builds/7403">https://build.macports.org/builders/ports-10.6_i386_legacy-watcher/builds/7403</a><br></div><div><a href="https://build.macports.org/builders/ports-10.5_ppc_legacy-watcher/builds/6553">https://build.macports.org/builders/ports-10.5_ppc_legacy-watcher/builds/6553</a><br></div><div><br></div><div>In all the stdio logs, I saw the following:<br></div><div><br></div><pre><span class="stdout">---> Fetching distfiles for bazel
</span><span class="stderr">DEBUG: elevating privileges for fetch: euid changed to 0, egid changed to 0.
DEBUG: dropping privileges: euid changed to 502, egid changed to 501.
DEBUG: Executing proc-pre-org.macports.fetch-fetch-0
Error: Failed to fetch bazel: No Java runtime present, requesting install.
2017-07-02 23:43:19.319 javac[76407:707] JLRequestRuntimeInstall: Error calling: CFMessagePortCreateRemote
child process exited abnormally
DEBUG: Error code: NONE
DEBUG: Backtrace: No Java runtime present, requesting install.
2017-07-02 23:43:19.319 javac[76407:707] JLRequestRuntimeInstall: Error calling: CFMessagePortCreateRemote
child process exited abnormally
while executing
"$pre $targetname"
Error: See /opt/local/var/macports/logs/_opt_bblocal_var_buildworker_ports_build_ports_devel_bazel/bazel/main.log for details.
Error: Follow <a href="https://guide.macports.org/#project.tickets">https://guide.macports.org/#project.tickets</a> to report a bug.
Error: Processing of port bazel failed
</span><span class="stdout">Build of 'bazel' failed.
</span><span class="stderr">./mpbb/mpbb: error: `install-port' failed to run successfully
</span><span class="header">program finished with exit code 1</span><br></pre><div><br></div><div>I'm guessing this was triggered by the pre-fetch phase of the port installation because there is a call to "javac" there via the "auto_execok" Tcl command.<br></div><div>Do the build machines have Java installed? As it stands right now, any changes to the Bazel port (or others like it) will cause build failures. So I'm wondering what can be done to avoid that.<br></div><div><br></div><div>Regards,<br></div><div>Mohamed<br></div></div></body></html>