diff options
| author |  ulfjack <ulfjack@google.com> | 2018-05-28 03:02:06 -0700 |
|---|---|---|
| committer |  Copybara-Service <copybara-piper@google.com> | 2018-05-28 03:03:37 -0700 |
| commit | cdf118a607ab179807cd39d0cafdb551859d1cd1 (patch) | |
| tree | 6e18d59f4dc9e675653028b710b79a761b2c202d /third_party/checker_framework_dataflow | |
| parent | 2ad044cbc0214ad1e1d7a30350e8b428dcd29bf4 (diff) | |
Enable --experimental_remote_spawn_cache by default
- It is now an error to specify the gRPC remote execution backend in
combination with a local disk or HTTP-based cache.
- It is now an error to specify both local disk and HTTP-based caches.
Note that before this CL, enabling the local disk cache silently disabled
remote execution - we now give an error in that case.
With these combination no longer being accepted, remote execution being enabled
now means that we only create a RemoteSpawnRunner, and don't provide a
SpawnCache. This is not a semantic change - we never created both.
In principle, it should be possible for users to combine local execution with
remote caching for actions that are marked local or no-remote, and still use
remote execution otherwise. However, Bazel cannot currently express this
combination of execution strategies.
RELNOTES: The --experimental_remote_spawn_cache flag is now enabled by default, and remote caching no longer needs --*_strategy=remote flags (it will fail if they are specified).
PiperOrigin-RevId: 198280398
Diffstat (limited to 'third_party/checker_framework_dataflow')
0 files changed, 0 insertions, 0 deletions