| commit | 49eb31b1880f56e2762b6cd480ae2cf732469561 | [log] [tgz] |
|---|---|---|
| author | Bo Zhang <zhangbodut@gmail.com> | Thu Oct 06 00:24:23 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Thu Oct 06 00:25:39 2022 -0700 |
| tree | 153c5087031b8c8b07bfec392aa63bd2a29438b9 | |
| parent | c82f80fd27b6ff9d27eee85076fe853133f7fd6d [diff] |
Throw explicit exception if experimental_split_coverage_postprocessing is used without experimental_fetch_all_coverage_outputs This closes https://github.com/bazelbuild/bazel/issues/13185 According to https://github.com/bazelbuild/bazel/commit/e411fa74176cdc54f84d62c189d042e9fb6d5c79, The flag --experimental_split_coverage_postprocessing depends on the flag --experimental_fetch_all_coverage_outputs being enabled, but if the former one is set without the latter one, Bazel throws a quite confusing NullPointerException. Now we throw an explicit exception with proper error message. Closes #16140. PiperOrigin-RevId: 479239693 Change-Id: I5afa0ae14a3f34a0a7b21fbf4badad3d1836da95
{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:
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
