Skip to content

Make --experimental_remote_cache_async not experimental and on by default #21578

@brentleyjones

Description

@brentleyjones

Description of the feature request:

It would be nice if the --experimental_remote_cache_async flag was no longer experimental and on by default. If that's not possible now, then issues should be identified and fixed as well in order to allow the flip.

Which category does this issue belong to?

Remote Execution

What underlying problem are you trying to solve with this feature?

Better build times when using a remote cache.

Which operating system are you running Bazel on?

No response

What is the output of bazel info release?

No response

If bazel info release returns development 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

Have you found anything relevant by searching the web?

No response

Any other information, logs, or outputs that you want to share?

No response

Metadata

Metadata

Assignees

Labels

P2We'll consider working on this in future. (Assignee optional)team-Remote-ExecIssues and PRs for the Execution (Remote) teamtype: feature request

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions