lol code coverage marks all my tracing::trace! statements as not covered because, well, I don't run tests with RUST_LOG=trace
which way would you go to solve that?
@fasterthanlime either run with trace, or compile the trace level out at compile time for tests
it’s either a cargo feature or a cfg string for tracing
@brk @fasterthanlime yeah the latter is what i'd do, and a second non-code-coverage test run with tracing enabled because i'm super paranoid about "oops that panic only happens when constructing trace logs"
@iximeow @brk I'm experimenting with https://docs.rs/tracing/latest/tracing/level_filters/index.html but it doesn't look like this excludes them from coverage
@fasterthanlime @iximeow @brk looks like there’s an experimental flag to ignore unused functions. maybe this is a fun yak to shave https://doc.rust-lang.org/rustc/instrument-coverage.html#-c-instrument-coverageoptions