| commit | e83d5f3c77d2b41a0ad2fb9c5a0fb1dfb5e912a7 | [log] [tgz] |
|---|---|---|
| author | Keith Smiley <keithbsmiley@gmail.com> | Fri Jul 15 06:23:29 2022 -0700 |
| committer | GitHub <noreply@github.com> | Fri Jul 15 13:23:29 2022 +0000 |
| tree | f372af450fc2dbd8f11e2b7db3f251f1dec67235 | |
| parent | daff327ea7923cf4032a52f6b63a44856dbeb0b8 [diff] |
Limit coverage to requested files (#1467) Bazel provides COVERAGE_MANIFEST which is a file we can pass through to llvm-cov to limit the files that we produce coverage for. Using this revealed the path-equivalence was backwards because we're using the coverage prefix map to disable absolute paths in code coverage info, but llvm-cov operates on absolute paths, so we have to remap the `.` in the coverage data to the full path so that llvm-cov understands the relative paths (which it absolutizes internal) from the manifest file. This feels a bit weird and ideally it could operate entirely on these relative paths instead. This has the side effect of excluding files that aren't part of bazel sources, which fixes https://github.com/bazelbuild/rules_rust/issues/1466 This should also improve interaction with `--instrumentation_filter`. Co-authored-by: UebelAndre <github@uebelandre.com>
This repository provides rules for building Rust projects with Bazel.
General discussions and announcements take place in the GitHub Discussions, but there are additional places where community members gather to discuss rules_rust.
Please refer to the full documentation.