-
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
NPE in CompletionFunction
#22741
Labels
P1
I'll work on this now. (Assignee required)
team-Remote-Exec
Issues and PRs for the Execution (Remote) team
type: bug
Comments
github-actions
bot
added
the
team-Remote-Exec
Issues and PRs for the Execution (Remote) team
label
Jun 13, 2024
coeuvre
added
P1
I'll work on this now. (Assignee required)
and removed
untriaged
labels
Jun 17, 2024
@bazel-io fork 7.2.1 |
@bazel-io fork 7.3.0 |
Wyverald
pushed a commit
that referenced
this issue
Jun 20, 2024
Fixes #22741. PiperOrigin-RevId: 643932127 Change-Id: Ia9566acb7b828224679ad57b71644281a8e52db4
Wyverald
pushed a commit
that referenced
this issue
Jun 20, 2024
Fixes #22741. PiperOrigin-RevId: 643932127 Change-Id: Ia9566acb7b828224679ad57b71644281a8e52db4
This was referenced Jun 20, 2024
github-merge-queue bot
pushed a commit
that referenced
this issue
Jun 20, 2024
Fixes #22741. PiperOrigin-RevId: 643932127 Change-Id: Ia9566acb7b828224679ad57b71644281a8e52db4 Co-authored-by: Googler <[email protected]>
github-merge-queue bot
pushed a commit
that referenced
this issue
Jun 21, 2024
Fixes #22741. PiperOrigin-RevId: 643932127 Change-Id: Ia9566acb7b828224679ad57b71644281a8e52db4 Co-authored-by: Googler <[email protected]> Co-authored-by: Yun Peng <[email protected]>
A fix for this issue has been included in Bazel 7.2.1 RC2. Please test out the release candidate and report any issues as soon as possible. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
P1
I'll work on this now. (Assignee required)
team-Remote-Exec
Issues and PRs for the Execution (Remote) team
type: bug
Description of the bug:
A failure during remote execution resulted in this server crash:
Which category does this issue belong to?
Remote Execution
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?
No response
What is the output of
bazel info release
?No response
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
?No response
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: