We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When trying to use the --experimental_remote_downloader flag with remote execution, bazel reports the following error:
--experimental_remote_downloader
ERROR: The remote downloader can only be used in combination with gRPC caching
bazel build //... --remote-executor="grpc://localhost:8980" --experimental_remote_downloader="grpc://localhost:8981"
Release 3.3.1
Linux
A workaround for this is to also provide --remote_cache="grpc://localhost:8980" assuming your remote execution endpoint is also your cache endpoint.
The text was updated successfully, but these errors were encountered:
I'm not sure exactly what your setup is, but here at Stripe we're using the remote downloader and remote executor together in dozens of workspaces.
Is it possible that this is a flag validation issue? If so, could the title be made more precise?
Sorry, something went wrong.
25e58ff
coeuvre
Successfully merging a pull request may close this issue.
Description of the problem / feature request:
When trying to use the
--experimental_remote_downloader
flag with remote execution, bazel reports the following error:Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
bazel build //... --remote-executor="grpc://localhost:8980" --experimental_remote_downloader="grpc://localhost:8981"
What version of bazel are you running?
Release 3.3.1
What operating system are you running Bazel on?
Linux
Any other information, logs, or outputs that you want to share?
A workaround for this is to also provide --remote_cache="grpc://localhost:8980" assuming your remote execution endpoint is also your cache endpoint.
The text was updated successfully, but these errors were encountered: