Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cherry-pick https://github.com/bazelbuild/bazel/commit/47696c94cac862ff80ece3873f4162f5815c7a32 #14701

Closed
blorente opened this issue Feb 3, 2022 · 2 comments · Fixed by #14842
Labels
team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website

Comments

@blorente
Copy link

blorente commented Feb 3, 2022

Description of the problem / feature request:

Please cherry-pick 47696c9 into the next 5.x release.

Feature requests: what underlying problem are you trying to solve with this feature?

The current 5.0 release calls some native interfaces to get pids that are not present in Apple Silicon machines with our current JDK. That commit files the issue.

Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.

Unfortunately, this reproduces with our internal JDK only. But we have validated that this commit fixes it.

What operating system are you running Bazel on?

macOS, in an M1 machine, with a custom JDK.

What's the output of bazel info release?

Both 5.0 and 4.2.2 repro this. In fact, every release up to (and including) 6.0.0-pre.20211110.1 reproduce it.

Any other information, logs, or outputs that you want to share?

Running bazel in the bazelbuild/examples repository, in cpp-tutorial/stage1, gives the following result:

INFO: Invocation ID: afc878b9-7dbf-4a07-a6a5-334406f5c07c
INFO: Analyzed target //main:hello-world (0 packages loaded, 0 targets configured).
INFO: Found 1 target...
Target //main:hello-world up-to-date:
  bazel-bin/main/hello-world
INFO: Elapsed time: 0.424s, Critical Path: 0.01s
INFO: 1 process: 1 internal.
INFO: Build completed successfully, 1 total action
FATAL: bazel crashed due to an internal error. Printing stack trace:
java.lang.RuntimeException: Unexpected Exception ''int com.google.devtools.build.lib.unix.ProcessUtils.getpid()'' when closing BEP transports, this is a bug.
        at com.google.devtools.build.lib.buildeventservice.BuildEventServiceModule.waitForBuildEventTransportsToClose(BuildEventServiceModule.java:490)
        at com.google.devtools.build.lib.buildeventservice.BuildEventServiceModule.closeBepTransports(BuildEventServiceModule.java:566)
        at com.google.devtools.build.lib.buildeventservice.BuildEventServiceModule.afterCommand(BuildEventServiceModule.java:581)
...
@Wyverald Wyverald added this to the 5.1 release blockers milestone Feb 3, 2022
@gregestren gregestren added the team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website label Feb 3, 2022
@brentleyjones
Copy link
Contributor

There are merged conflicts when I try to cherry-pick this, that I don't feel confident in resolving, so can someone else create the cherry-pick PR?

@Wyverald
Copy link
Member

I'll take a look. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team-OSS Issues for the Bazel OSS team: installation, release processBazel packaging, website
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants