-
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
[7.2.0] Unrecoverable error while evaluating node 'REPOSITORY_DIRECTORY:@@WORKSPACE.bazel' #22740
Comments
It would be great if you could test with Bazel 7.0 and Bazel 7.1 as well |
7.1.1 (7.1.0 was deadlocking due to the restartless fetch changes):
7.0.0
|
Looks like something is depending on the (It's a known problem that trying to refer to a repo named "WORKSPACE" or "WORKSPACE.bazel" would cause a crash, but we never got around to fixing that. Incidentally, |
Aaaaah, I think the thing that confused bazel terribly here is that our bazel wrapper gained the following code (python):
creating a symlink I don't think there's a bazel bug here per se, but crashing with an internal error and a ClassCastException is not exactly helpful either. As a user, my expectation would be that regardless of how I try to break bazel, it's not crashing. |
Description of the bug:
My colleague hit this internal exception while developing on our bazel-wrapper script.
Our test run first builds some targets (works), and then runs a test invocation, which immediately crashes.
WORKSPACE.bazel
exists, but is empty. Maybe the in-development wrapper messes some paths up, but bazel shouldn't crash like this.We've not attempted to debug this further, hoping that the exception stack trace is enough for you to identify a problem on your side.
CC @redsun82
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.
If the stack trace isn't enough to debug this, we can try working out a reproducer.
Which operating system are you running Bazel on?
Linux
What is the output of
bazel info release
?development version
If
bazel info release
returnsdevelopment version
or(@non-git)
, tell us how you built Bazel.bazelisk, commit 7628649 (the tip of the 7.2.1 release branch a few days ago), basically 7.2.0 with one commit applied.
What's the output of
git remote get-url origin; git rev-parse HEAD
?N/A
If this is a regression, please try to identify the Bazel commit where the bug was introduced with bazelisk --bisect.
We've not tried to identify if this is a regression yet
Have you found anything relevant by searching the web?
Not looked yet
Any other information, logs, or outputs that you want to share?
No response
The text was updated successfully, but these errors were encountered: