-
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
--noremote_accept_cached cannot be used with remote downloader as of Bazel 5.0 #15934
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
sgowroji
added
more data needed
team-Remote-Exec
Issues and PRs for the Execution (Remote) team
labels
Jul 21, 2022
Hello @clint-stripe, Could you please provide complete steps to reproduce the above issue. Thanks! |
@sgowroji the steps to reproduce are given in the repo I linked, but I can provide them here again:
This is a complete repro: the error occurs immediately when Bazel downloads the repository referenced in the WORKSPACE file. |
Is this related / the same as #15527? |
Maybe. I will look into both. |
meisterT
added
P2
We'll consider working on this in future. (Assignee optional)
and removed
untriaged
labels
Jul 28, 2022
coeuvre
added a commit
to coeuvre/bazel
that referenced
this issue
Aug 3, 2022
Instead of guessing when to use remote/disk part, combined cache now uses read/write cache policy provided by the context. The call sites can change the policy based on the requirements. Fixes bazelbuild#15934. But unfortunately, I am not able to add an integration test for it because our own remote worker doesn't support the asset API.
coeuvre
added a commit
to coeuvre/bazel
that referenced
this issue
Aug 3, 2022
Instead of guessing when to use remote/disk part, combined cache now uses read/write cache policy provided by the context. The call sites can change the policy based on the requirements. Fixes bazelbuild#15934. But unfortunately, I am not able to add an integration test for it because our own remote worker doesn't support the asset API.
ShreeM01
added a commit
that referenced
this issue
Aug 8, 2022
Instead of guessing when to use remote/disk part, combined cache now uses read/write cache policy provided by the context. The call sites can change the policy based on the requirements. Fixes #15934. But unfortunately, I am not able to add an integration test for it because our own remote worker doesn't support the asset API. Closes #16039. PiperOrigin-RevId: 465577383 Change-Id: I99effab1cdcba0890671ea64c4660ea31b059ce7 Co-authored-by: Chi Wang <chiwang@google.com>
coeuvre
added a commit
to coeuvre/bazel
that referenced
this issue
Aug 16, 2022
Instead of guessing when to use remote/disk part, combined cache now uses read/write cache policy provided by the context. The call sites can change the policy based on the requirements. Fixes bazelbuild#15934. But unfortunately, I am not able to add an integration test for it because our own remote worker doesn't support the asset API. Closes bazelbuild#16039. PiperOrigin-RevId: 465577383 Change-Id: I99effab1cdcba0890671ea64c4660ea31b059ce7
ShreeM01
pushed a commit
that referenced
this issue
Aug 16, 2022
Instead of guessing when to use remote/disk part, combined cache now uses read/write cache policy provided by the context. The call sites can change the policy based on the requirements. Fixes #15934. But unfortunately, I am not able to add an integration test for it because our own remote worker doesn't support the asset API. Closes #16039. PiperOrigin-RevId: 465577383 Change-Id: I99effab1cdcba0890671ea64c4660ea31b059ce7
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:
We use the Remote Downloader (the
--experimental_remote_downloader
flag) to enforce security invariants in our builds and reduce dependencies on external hosts.We also occasionally run builds with
--noremote_accept_cached
.This flag is documented as:
This means we still expect to be able to use the CAS (which underlies the remote downloader service), but we do not want actions themselves to be cached.
As of Bazel 5.0 (specifically, #13769, from the
git bisect
I did), this fails with an error that Bazel retrieved an empty file (the e3b0c... hash), rather than the one specified in the WORKSPACE file.What's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
https://github.com/clint-stripe/remote-downloader-cache
We're using a different implementation of the remote cache and downloader internally, but this repo shows the same issue occurs with the open source implementation at https://github.com/buchgr/bazel-remote.
(This repro doesn't have Bazel run with
--incompatible_remote_results_ignore_disk
, which was added in that CL, but it does not change the behavior here either.)Which operating system are you running Bazel on?
darwin, linux
What is the output of
bazel info release
?release 5.0.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 master; git rev-parse HEAD
?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: