-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Constant "remote cache eviction error" message #22220
Labels
P2
We'll consider working on this in future. (Assignee optional)
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
May 2, 2024
👋 Is this different than #18696? |
coeuvre
added
P2
We'll consider working on this in future. (Assignee optional)
and removed
untriaged
labels
May 7, 2024
Can you share the gRPC log, especially the It also worth trying whether this is fixed by upcoming 7.2 release which includes eda0fe4. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
P2
We'll consider working on this in future. (Assignee optional)
team-Remote-Exec
Issues and PRs for the Execution (Remote) team
type: bug
Description of the bug:
Hello!
We've been using the various flags related to addressing remote cache evictions in multiple projects successfully. I noticed an interesting behavior in one of our repos lately after taking a closer look at our CI logs. We consistently see the same action/invocation failing with a remote cache eviction error and then recovering by itself.
We run the
bazel-diff
tool in abazel run
invocation, which always fails with the same missing digestbazel-out/k8-fastbuild/bin/external/rules_java/toolchains/platformclasspath.jar
. When Iquery the remote cache for that particular digest using
tools_remote
, I get the correct blob returned. This means that the blob is in our remote cache, but somehow Bazel thinks it's not? I have an execution log for the specific situation as well if needed. I attached the part of the log where I could find two instances of this particular digest.Bazel invocation log:
Execution log:
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.
I wasn't able to reproduce this easily just yet, but it definitely requires a remote cache with the following flags enabled:
The rule that always fails is also pretty straightforward:
And the invocation looks like this:
Which operating system are you running Bazel on?
Linux
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.7.1.1
What's the output of
git remote get-url origin; 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: