Closed danieleades closed 1 year ago
Thanks. Addressed in v0.5.21.
is the 'doctests' making use of any other unstable features or can that now be stabilised too?
instrument-coverage for doctests requires unstable --persist-doctests
too.
https://doc.rust-lang.org/nightly/rustc/instrument-coverage.html#including-doc-tests
This new release 0.5.21 is not working with stable rust anymore.
$ cargo llvm-cov --all --all-features --lcov --output-path lcov.info
error: the `-Z` flag is only accepted on the nightly channel of Cargo, but this is the `stable` channel
See https://doc.rust-lang.org/book/appendix-07-nightly-rust.html for more information about Rust release channels.
error: process didn't exit successfully: `/home/pksunkara/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/bin/cargo test -Z doctest-in-workspace --tests --manifest-path /home/pksunkara/Coding/project/Cargo.toml --target-dir /home/pksunkara/Coding/project/target/llvm-cov-target --all --all-features` (exit status: 101)
0.5.20 works though.
Oh, sorry for the breakage! Fixed in 0.5.22 and yanked 0.5.21.
when running the following command-
i see this warning-
if i take that at face value, does that mean the flag can be removed? is the 'doctests' making use of any other unstable features or can that now be stabilised too?