You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Summary:
Closes#776.
Implements support for persistent workers in remote builds using the Bazel remote execution protocol and the approach documented in the Bazel remote persistent workers proposal:
https://github.com/bazelbuild/proposals/blob/main/designs/2021-03-06-remote-persistent-workers.md
The Bazel remote persistent worker protocol includes an automatic fallback in cases where the remote execution system does not yet support persistent workers. To that end actions take the shape
```
WORKER WORKER_ARGS... REQUEST_ARGS_FILE
```
The remote execution system separates worker arguments on the command-line from request arguments in the response file and adds the `--persistent_worker` flag.
Pull Request resolved: #787
Test Plan: Test added in D68157749.
Reviewed By: IanChilds
Differential Revision: D65213349
Pulled By: KapJI
fbshipit-source-id: 79d219a06c08fad7d16976c6c9e5a6815dd073df
/// * `allow_hybrid_fallbacks_on_failure`: Whether to allow fallbacks when the result is failure (i.e. the command failed on the primary, but the infra worked)
87
87
/// * `use_windows_path_separators`: Whether to use Windows path separators in command line arguments
88
88
/// * `use_persistent workers`: Whether to use persistent workers for local execution if they are available
89
+
/// * `use_bazel_protocol_remote_persistent_workers`: Whether to use persistent workers for remote execution via the Bazel remote persistent worker protocol if they are available
89
90
/// * `allow_cache_uploads`: Whether to upload local actions to the RE cache
90
91
/// * `max_cache_upload_mebibytes`: Maximum size to upload in cache uploads
91
92
/// * `experimental_low_pass_filter`: Whether to use the experimental low pass filter
0 commit comments