-
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
Unrecoverable error using bzlmod #19632
Labels
team-Configurability
platforms, toolchains, cquery, select(), config transitions
type: bug
untriaged
Comments
fmeum
added a commit
to fmeum/bazel
that referenced
this issue
Oct 9, 2023
When a label pointing to an unavailable repository is specified as a transition's input or output, an early error is raised instead of crashing during transition evaluation. Fixes bazelbuild#19632 Closes bazelbuild#19634. PiperOrigin-RevId: 570634319 Change-Id: Icda2946313898db2372484b4f845aafcf5a8b272
fmeum
added a commit
to fmeum/bazel
that referenced
this issue
Oct 9, 2023
When a label pointing to an unavailable repository is specified as a transition's input or output, an early error is raised instead of crashing during transition evaluation. Fixes bazelbuild#19632 Closes bazelbuild#19634. PiperOrigin-RevId: 570634319 Change-Id: Icda2946313898db2372484b4f845aafcf5a8b272
meteorcloudy
pushed a commit
that referenced
this issue
Oct 9, 2023
…19764) When a label pointing to an unavailable repository is specified as a transition's input or output, an early error is raised instead of crashing during transition evaluation. Fixes #19632 Closes #19634. PiperOrigin-RevId: 570634319 Change-Id: Icda2946313898db2372484b4f845aafcf5a8b272 Fixes #19641
A fix for this issue has been included in Bazel 6.4.0 RC2. Please test out the release candidate and report any issues as soon as possible. Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
team-Configurability
platforms, toolchains, cquery, select(), config transitions
type: bug
untriaged
Description of the bug:
While making rules_dotnet bzlmod compatible I encountered an Bazel crash:
Reproduction is available at bazel-contrib/rules_dotnet#387 by running
bazel test //... --enable_bzlmod
cc @fmeum
Which category does this issue belong to?
No response
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
No response
Which operating system are you running Bazel on?
Linux Fedora 38
What is the output of
bazel info release
?release 6.3.2
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?
No response
Any other information, logs, or outputs that you want to share?
No response
The text was updated successfully, but these errors were encountered: