| commit | a2ebdf71a90b1e2df6502929ad86251904890fcf | [log] [tgz] |
|---|---|---|
| author | Charles Mita <cmita@google.com> | Mon Feb 19 07:33:12 2024 -0800 |
| committer | Copybara-Service <copybara-worker@google.com> | Mon Feb 19 07:34:24 2024 -0800 |
| tree | 31bc8225d2c9e4011bbf123e0398b3ffdbdc78a3 | |
| parent | 7d3b3108b33b4821d6975621ef68a1d3331ca6fd [diff] |
Pass the name of the classpath manifest jar to JacocoCoverageRunner When the java classpath exceeds the limit, we create a manifest JAR and pass that on the classpath. JacocoCoverageRunner knows how to extract information from this JAR. But if another JAR ends up on that classpath, it confuses the coverage runner which is expecting only a single jar in this case. This changes the java_stub_template file to export the name of the created manifest jar so the coverage runner can extract it. We also change the template file so the relevant exports don't occur in the middle of a larger function. It's possible this is somewhat overengineered and that we could always rely on the manifest jar always being the first one discovered by the coverage runner, but it is not totally obvious to me that that will always be true. Fixes #21268 Closes #21365. PiperOrigin-RevId: 608333782 Change-Id: I9895689fd9d771c9198e36bef222a9f86ada573e
{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
