| commit | db7ff2158ecfd9ff4ae2ea2093087c092a1d26e5 | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Fri Apr 29 13:49:49 2022 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri Apr 29 13:51:11 2022 -0700 |
| tree | 3a71f2247b5abe5951cc4a69c3928d75850418f7 | |
| parent | 321b42e177ef48e703f379a7f35835c9ab564280 [diff] |
Don't skip filtering when manifest of source-file paths is empty When a coverage entry doesn't correspond to a file listed in execPathsOfUninstrumentedFiles, it's discarded. However, since this class has a constructor which takes no arguments and sets execPathsOfUninstrumentedFiles to an empty-set. But this leads to those same no-filtering behavior when the constructor is passed an empty list of valid source files. Instead, the "leave as is" behavior should be conditioned on `execPathsOfUninstrumentedFiles == null`, and an empty set should be treated consistently with other sets with no matching items. RELNOTES: None. PiperOrigin-RevId: 445497757
{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
