Fix infinite hang on Windows compilation actions in WaitableProcess. Occasionally on Windows, Bazel compilation actions (such as MSVC cl.exe) get stuck in an infinite wait in the Bazel server even after the compiler process has finished. When cl.exe runs, it can launch background child processes such as Microsoft's telemetry uploader (vctip.exe), which can enter an unkillable zombie state inside the Windows Job Object. Because Bazel previously waited with an INFINITE timeout for JOB_OBJECT_MSG_ACTIVE_PROCESS_ZERO after calling TerminateJobObject, any stuck child process caused the entire build server to hang forever. Replace INFINITE with a finite 5-second timeout (kJobCompletionTimeoutMsec) when calling GetQueuedCompletionStatus in WaitableProcess::WaitFor after the primary process has terminated and TerminateJobObject has been invoked. This allows Bazel to proceed after a short grace period even if background subprocesses like vctip.exe refuse to terminate. Fixes https://github.com/bazelbuild/bazel/issues/15094. PiperOrigin-RevId: 971912626 Change-Id: I8e289d376ee7ac4bf61de7abd7a32f64893eb85d
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
