diff options
| author |  Laszlo Csomor <laszlocsomor@google.com> | 2017-04-26 13:41:56 +0200 |
|---|---|---|
| committer |  Vladimir Moskva <vladmos@google.com> | 2017-04-26 18:04:29 +0200 |
| commit | d12fb7a4864ab0a192c3d47c3443824eccbb4c74 (patch) | |
| tree | 501bccd7995a65a035b8430ba3c5d2f1d2f8bfa2 /src/test/java/com/google/devtools/build/lib/rules/cpp/LTOBackendActionTest.java | |
| parent | a5f82e5e249aa8bcc356928db9118371fe22dccf (diff) | |
Bazel client, Windows: impl. server->IsStillAlive
Implement proper aliveness check for the Bazel
server.
This allows detecting a server death that occurs
after the Java process started but before it
started the gRPC server.
On other platforms we open an anonymous pipe, let
the server inherit the writing end, close the
writing end in the client, and attempt to read
non-blockingly in order to check if the server is
still alive.
This approach fails on Windows because anonymous
pipes are always blocking. Named pipes support
asynchronous access but it's much simpler to just
check if the process exited. GetProcessTimes looks
like a reliable way to do so, and that's what we
use on Windows now.
Fixes https://github.com/bazelbuild/bazel/issues/2817
Change-Id: Ic24577d8440eb0c8188c852e2501ce1e254ba9fd
PiperOrigin-RevId: 154283585
Diffstat (limited to 'src/test/java/com/google/devtools/build/lib/rules/cpp/LTOBackendActionTest.java')
0 files changed, 0 insertions, 0 deletions