Prevent new commands from starting if Bazel is in the middle of crashing: crashing can take quite a long time during clean-up, and it's confusing if another command runs in the middle of it. This became much more likely after https://github.com/bazelbuild/bazel/commit/5ebcf97e655797cf3715806fff55e7fa3c5a61b9, since the command thread is interrupted in a crash now, so control is returned to the caller.
PiperOrigin-RevId: 383564388
diff --git a/src/test/java/com/google/devtools/build/lib/remote/RemoteModuleTest.java b/src/test/java/com/google/devtools/build/lib/remote/RemoteModuleTest.java
index 5b41d27..8957935 100644
--- a/src/test/java/com/google/devtools/build/lib/remote/RemoteModuleTest.java
+++ b/src/test/java/com/google/devtools/build/lib/remote/RemoteModuleTest.java
@@ -118,7 +118,8 @@
productName);
BlazeWorkspace workspace = runtime.initWorkspace(directories, BinTools.empty(directories));
Command command = BuildCommand.class.getAnnotation(Command.class);
- return workspace.initCommand(command, options, new ArrayList<>(), 0, 0, ImmutableList.of());
+ return workspace.initCommand(
+ command, options, new ArrayList<>(), 0, 0, ImmutableList.of(), s -> {});
}
static class CapabilitiesImpl extends CapabilitiesImplBase {
