Split coverage post-processing into its own spawn This change fixes b/79147227 by introducing a flag that makes coverage post-processing happen in its own spawn. The runfiles in the coverage spawn are those of the LCOV merger instead of the test runfiles. The flag introduced is --experimental_split_coverage_postprocessing which depends on the flag --experimental_fetch_all_coverage_outputs being enabled too. PiperOrigin-RevId: 339699090
{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.
Follow our tutorials:
See CONTRIBUTING.md
