-
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
Unable to execute bazel info
without a module file
#24239
Comments
Digging a little deeper, the error was caused by skylib being referenced before skylib had been loaded in a workspace-based build. |
The precise error being:
|
Yes, looks like a few places are creating an I'll add some checks for that. |
I think I have a better fix but I can't reproduce the issue, I'll put up a draft PR in a few minutes, would you be able to test it? |
Sure. I'd be happy to |
…ations. Part of bazelbuild#24239. PiperOrigin-RevId: 694147129 Change-Id: I7d0a9c129c34725d0843eb7ec87b46c657d168d8
Take a look at #24241 |
Works on my machine :) Thank you for the more complete fix! |
okay, I'll split it out and merge mine, and drop #24240. |
…ations. Fixes bazelbuild#24239. Closes bazelbuild#24241. PiperOrigin-RevId: 694147129 Change-Id: I7d0a9c129c34725d0843eb7ec87b46c657d168d8
Okay, fix is submitted at head, @shs96c can you handle the cherrypick requests for 7.4.x and 8.0.0? |
Description of the bug:
See the build logs from this PR in rules_jvm_external
The execution of
bazel info
fails with:Which category does this issue belong to?
Core
What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
rules_jvm_external
and checks outd8cc6c07f2c1c61276f46e6f03b270db497e98fe
.cd examples/simple
bazel info
Which operating system are you running Bazel on?
macOS and Linux
What is the output of
bazel info release
?7.4.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 HEAD
?If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.
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: