Lazy output stream for test.xml, does not produce a file if no test xml data was produced This fixes #5289. The general problem is, if an exception is thrown during creation of the `TestSuiteModel`, the test runner will exit, closing off the OutputStream it had created for writing the test.xml. Unfortunately, if nothing was actually written to the stream, closing it will create a 0-byte test.xml on disk regardless. This PR wraps the OutputStream in a lazy producer, only creating the actual stream if something was written to it. This guarantees test.xml will contain actual content. Closes #6000. PiperOrigin-RevId: 211799139
{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.