You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using a doctest in a README.md file marked with should_panic, tarpaulin executes it but does not seem to parse out the should_panic as it ends in failure. Removing the should_panic flag (and removing the failing assert) and it passes as expected.
My repo is very small so can probably be used as a reproducible sample:
This looks like a duplicate of #924 and this comment explains what is happening #924 (comment) aside from better upstream support in rustc or the attribute finding code expanding preprocessor includes of text the only approach I could think of would be a hacky flag like --doctests-always-pass
Appreciate the fast response. Other than disabling my README test, any ideas for how to get tarpaulin to just skip this test, but not cargo test? Otherwise I'll probably just have to disable the README test for now, thx.
When using a doctest in a README.md file marked with
should_panic
, tarpaulin executes it but does not seem to parse out theshould_panic
as it ends in failure. Removing theshould_panic
flag (and removing the failing assert) and it passes as expected.My repo is very small so can probably be used as a reproducible sample:
README:
https://github.com/nu11ptr/assert_unordered/blame/master/README.md#L25
Code that triggers README test:
https://github.com/nu11ptr/assert_unordered/blob/master/src/lib.rs#L40
I was expecting (or at least hoping) the test would pass like it does when executed with
cargo test
The text was updated successfully, but these errors were encountered: