-
Notifications
You must be signed in to change notification settings - Fork 4k
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
Crash when using module extension #18641
Comments
The cause of the crash is that you're calling a build rule (instead of a repo rule) from a module extension. Nevertheless, we shouldn't crash Bazel, but provide a helpful error message instead. |
This code seems to cause a similar crash. Is the cause the same? https://github.com/garymm/bazel-bugs/tree/master/llvm-toolchain-starlark If not I can file another issue. |
That one looks different. Please file another issue. |
Oh alright, I see. How would you go about initializing a custom toolchain in a Module then? (Set includes, flags,...) |
Fixes: #18641 PiperOrigin-RevId: 546092727 Change-Id: I66365813a40390ec61a1a0565b06655b3ca50fcd
Fixes: #18641 PiperOrigin-RevId: 546092727 Change-Id: I66365813a40390ec61a1a0565b06655b3ca50fcd
Description of the bug:
While trying to use the Bazel Module extension feature, I found a crash and I have not idea what's causing it.
I'm configuring the module
build_tools_reloaded
(a custom toolchain) from theTEST_PARTITION
project.The crash :
The command:
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
TEST_PARTITION/MODULE.bazel
:build_tools_reloaded/extensions/extensions.bzl
:build_tools_reloaded/toolchain/rules.bzl
:Which operating system are you running Bazel on?
Windows
What is the output of
bazel info release
?release 6.2.0
If
bazel info release
returnsdevelopment version
or(@non-git)
, tell us how you built Bazel.No response
What's the output of
git remote get-url origin; git rev-parse master; git rev-parse HEAD
?No response
Is this a regression? If yes, please try to identify the Bazel commit where the bug was introduced.
No response
Have you found anything relevant by searching the web?
Maybe similar to : #14974
Any other information, logs, or outputs that you want to share?
No response
The text was updated successfully, but these errors were encountered: