Non-workspace path dependencies are included in reports and totals

[detly]

If I have a workspace package that also has non-workspace path dependencies, the coverage report from cargo llvm-cov --workspace includes the non-workspace sources. I don't know if this is expected or not, but it was surprising to me, and whether it happens is affected by details of the code.

Here's an example project if it helps. The structure this:

.
├── Dockerfile
├── one
│  ├── Cargo.toml
│  ├── ones-child
│  │  ├── Cargo.toml
│  │  └── src
│  │     └── lib.rs
│  └── src
│     └── lib.rs
└── two
   ├── Cargo.toml
   └── src
      └── lib.rs

The only interesting manifest is one/Cargo.toml:

[package]
name = "one"
version = "0.1.0"
edition = "2021"

[dependencies]
ones-child = { path = "ones-child" }
two = { path = "../two" }

[workspace]
members = [
    "ones-child",
]

If one never calls two, two's sources are not included in the report (example project job #4908791850):

Filename                      Regions    Missed Regions     Cover   Functions  Missed Functions  Executed       Lines      Missed Lines     Cover    Branches   Missed Branches     Cover
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
ones-child/src/lib.rs               4                 0   100.00%           3                 0   100.00%           8                 0   100.00%           0                 0         -
src/lib.rs                          4                 0   100.00%           3                 0   100.00%           8                 0   100.00%           0                 0         -

If one DOES call two, two's sources ARE included (job #4910063504):

Filename                      Regions    Missed Regions     Cover   Functions  Missed Functions  Executed       Lines      Missed Lines     Cover    Branches   Missed Branches     Cover
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
one/ones-child/src/lib.rs           4                 0   100.00%           3                 0   100.00%           8                 0   100.00%           0                 0         -
one/src/lib.rs                      4                 0   100.00%           3                 0   100.00%           8                 0   100.00%           0                 0         -
two/src/lib.rs                      1                 0   100.00%           1                 0   100.00%           3                 0   100.00%           0                 0         -

The totals are a bit variable too - if one's tests cover two's code, even if two has zero coverage itself, it will be reported as 100% covered.

Seems related to #31.

• Rust 1.71.1
• cargo-llvm-cov 0.5.27
• run in Docker image rust:1.71.1-slim (Debian Bullseye)