ExecutionTool: close output file of "--explain" Close the OutputStream of "explanationHandler" after the handler is uninstalled. This guarantees that Bazel releases this file promptly, instead of relying on the GC and finalizers to do so. Closing streams is important to avoid stream contention which may prevent deleting files. (Open files may not be deleted on Windows.) I (laszlocsomor@) am not currently unaware of any such contention bugs in this code, but we have seen intermittent file deletion failures on Windows, so eliminating a potential source of such a bug should not hurt. RELNOTES: none PiperOrigin-RevId: 222545449
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel only rebuilds 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.
Follow our tutorials:
See CONTRIBUTING.md
Bazel is released in ‘Beta’. See the product roadmap to learn about the path toward a stable 1.0 release.