-
Notifications
You must be signed in to change notification settings - Fork 4.4k
no-remote and no-remote-cache are affecting the disk cache #13621
Copy link
Copy link
Closed
Labels
P1I'll work on this now. (Assignee required)I'll work on this now. (Assignee required)team-Remote-ExecIssues and PRs for the Execution (Remote) teamIssues and PRs for the Execution (Remote) teamtype: bug
Description
Description of the problem / feature request:
When an action is tagged with no-remote or no-remote-cache, it's not properly using the disk cache. Only with no-cache should it exclude the disk cache as well.
Bugs: what's the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
bazel build --disk_cache=/tmp/disk_cache -- //some/cacheable:target
bazel clean
bazel build --disk_cache=/tmp/disk_cache --modify_execution_info='.*=+no-remote-cache' -- //some/cacheable:targetThe second build won't check the disk cache.
What operating system are you running Bazel on?
macOS 11.4
What's the output of bazel info release?
4.1.0, but is still broken at HEAD.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
P1I'll work on this now. (Assignee required)I'll work on this now. (Assignee required)team-Remote-ExecIssues and PRs for the Execution (Remote) teamIssues and PRs for the Execution (Remote) teamtype: bug