| commit | e6aeecd2db3ae5f43bfdc186074d79255d8907f8 | [log] [tgz] |
|---|---|---|
| author | Googler <noreply@google.com> | Mon May 17 06:12:56 2021 -0700 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon May 17 06:13:44 2021 -0700 |
| tree | c1c81d21dbb4036ba9df5c53066924956ff19c09 | |
| parent | 1df4c71a9cf52f2dd24c4a10da75bb88631e7fde [diff] |
Don't require that tests output to bin (instead of genfiles) for coverage getInstrumentedFileManifest asserts `ruleContext.getRule().hasBinaryOutput()`. However, that doesn't assert that the target has an executable output. Rather, it asserts that the target's output goes to bin instead of genfiles. That's the preferred convention, but if a test sets `output_to_genfiles` for some reason (even though it probably shouldn't), having that return `InstrumentedFilesInfo` will cause it to suddenly start crashing in coverage mode. Which is pretty confusing. RELNOTES: None. PiperOrigin-RevId: 374180811
{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
