tree f372af450fc2dbd8f11e2b7db3f251f1dec67235
parent daff327ea7923cf4032a52f6b63a44856dbeb0b8
author Keith Smiley <keithbsmiley@gmail.com> 1657891409 -0700
committer GitHub <noreply@github.com> 1657891409 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJi0WpRCRBK7hj4Ov3rIwAAaQgIAIcS+hM08+t2kuRhcp8Bd+3f
 1t+hjc7e8rrxYzXZbNiVW1CzY2TPFsYtp24k/+L/JBQF8lfIV9R3fhvp4hMKeOU6
 V6WrOWz2NNQWxzVLE7ALWOQ1epLmQe4ZV0WkuyAZCW4KOdiRN40J1YFITLzs/AN4
 NCgXeUDoBegL+2H+xH63w6q6Q+HCRLuqWwev854/YYyDG6nsRzCQ6tXD/Z0sS4Yh
 8gNlIh42+7IWcacmdZNZwlgbi7BoCA0jm3qwHFScBQIq2Tp+cilibxwfwVRlbb4y
 FqPesEnoLQ9r+5KTzqOREFLh32VzZWRmJ7/eWcH0hAZ8p819TWxW4z+8HZmtke4=
 =Tja7
 -----END PGP SIGNATURE-----
 

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>