| commit | 21179b2a82154b870ad8c5a7ad22b4662067cb29 | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Fri May 29 10:22:29 2020 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Fri May 29 10:23:46 2020 -0700 |
| tree | 89dc249b84488929d5fe0bc653151d15b78541b7 | |
| parent | 8188ccf5f653d2c110a4196861288f96607ddf56 [diff] |
Forward InstrumentedFilesProvider from all dependencies by default (conditioned on flag) Currently, the entire dependency chain between a test and whatever rule compiles the source files must provide InstrumentedFilesInfo. Getting coverage correct for a given language requires not only rules that handle source files in that language to be correctly configured, but all rules in the dependency chain between the test and the source files must explicitly support coverage collection. Often, a rule's immediate dependencies are all one of: * Source files (which don't provide InstrumentedFilesProvider) * Rule targets which might provide either code or binaries which might be executed at runtime In those cases, forwarding InstrumentedFilesProvider from the dependencies is the correct behavior. Tool dependencies (ones in host/exec config) can be excluded, since code/binaries provided by those dependencies are not executed at runtime. If InstrumentedFilesProvider is forwarded from a dependency incorrectly and something in that dependency's transitive dependencies is matched by --instrumentation_filter, the downside is that the user may end up with correct runtime coverage data for an overly-large list of source files. The extraneous entries will note there is no coverage data for that file. That seems possibly better than the downside of the current default, that coverage data which could be correctly gathered is potentially omitted. The new behavior is enabled with the flag --experimental_forward_instrumented_files_info_by_default. RELNOTES: Add experiment flag to forward InstrumentedFilesInfo from non-tool deps by default. PiperOrigin-RevId: 313804469
{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
