Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

experimental_use_coverage_metadata_files #2082

Open
UebelAndre opened this issue Jul 27, 2023 · 0 comments
Open

experimental_use_coverage_metadata_files #2082

UebelAndre opened this issue Jul 27, 2023 · 0 comments

Comments

@UebelAndre
Copy link
Collaborator

UebelAndre commented Jul 27, 2023

experimental_use_coverage_metadata_files is a flag to have coverage tooling added as coverage_common.instrumented_files_info.metadata_files (taking advantage of bazelbuild/bazel#18697) instead of reporting tools like llvm-cov and llvm-profdata as runfiles to each test. To enable this flag pass the following:

--@rules_rust//rust/settings:experimental_use_coverage_metadata_files

Note that this flag is only supported on Bazel version >=6.3.0

UebelAndre added a commit that referenced this issue Jul 28, 2023
This change introduces `experimental_use_coverage_metadata_files`
(#2082) which is required
to support
[--experimental_split_coverage_postprocessing](https://bazel.build/reference/command-line-reference#flag--experimental_split_coverage_postprocessing)'

Changes:
- Implemented coverage collection logic in Rust.
- Added a flag
`--@rules_rust//rust/settings:experimental_use_coverage_metadata_files`
to toggle the changes necessary for supporting
`--experimental_split_coverage_postprocessing`.
- Added regression testing in CI to test
`--experimental_split_coverage_postprocessing`.
UebelAndre added a commit that referenced this issue Aug 28, 2023
ttiurani pushed a commit to ttiurani/rules_rust that referenced this issue Sep 15, 2023
github-merge-queue bot pushed a commit that referenced this issue Sep 3, 2024
Now that the min tested Bazel version is `7.3.1`
(#2812) this flag can
safely be flipped.

Relates to #2082
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant