Switching to Watcher API instead of wait_for_completion, in preparation for

deprecating the wait_for_completion field.

Note on errors: in the RemoteWorker, I currently handle all errors as onError of the watch call. Other options are: pass them as the operation error field, and pass some of them as the onError of the execute call. For now, I'm just using the simplest option; the Bazel client is ready to handle all possible options.

RELNOTES: none
PiperOrigin-RevId: 158974207

1 files changed, 0 insertions, 1 deletions

diff --git a/src/main/java/com/google/devtools/build/lib/remote/RemoteSpawnRunner.java b/src/main/java/com/google/devtools/build/lib/remote/RemoteSpawnRunner.java
index 383667437d..412031bb1b 100644
--- a/src/main/java/com/google/devtools/build/lib/remote/RemoteSpawnRunner.java
+++ b/src/main/java/com/google/devtools/build/lib/remote/RemoteSpawnRunner.java
@@ -115,7 +115,6 @@ final class RemoteSpawnRunner implements SpawnRunner {
             ExecuteRequest.newBuilder()
                 .setInstanceName(options.remoteInstanceName)
                 .setAction(action)
-                .setWaitForCompletion(true)
                 .setTotalInputFileCount(inputMap.size())
                 .setSkipCacheLookup(!options.remoteAcceptCached);
         result = executor.executeRemotely(request.build()).getResult();