-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
FATAL: bazel crashed due to an internal error. - Platforms #12879
Comments
The crash is concerning and I'll address it immediately. Bazel shouldn't crash, it should fail gracefully and report an error. The good news is, there's a simple fix: the correct type of target to use in
This will correctly report that the target can't be built. |
provider. Also update PlatformProviderUtils to work directly with Lists. This prevents a few types of crash that can occur from having null values in a List. Fixes bazelbuild#12879.
@holaworlds This is a similar error message but a different underlying cause. Please open a new issue with details on how to reproduce the error. |
Description of the problem / feature request:
Crash NullPointerException
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Run
bazelisk build :main
with Bazel 4.0.0 on MacOS with the followingBUILD
file:What operating system are you running Bazel on?
MacOS or Linux
What's the output of
bazel info release
?Have you found anything relevant by searching the web?
No.
Any other information, logs, or outputs that you want to share?
See attachment: testcase.tar.gz
The text was updated successfully, but these errors were encountered: