Eugene

I've got [the repro](https://github.com/Eugeny/cargo-llvm-cov-repro) ready and then tried putting `--no-report` _after_ `run`, and it worked! Shame on me. Might still be unexpected behaviour however, that: * `--no-report` before `run` is...

> This is https://github.com/taiki-e/cargo-llvm-cov/issues/151, and will be fixed by https://github.com/taiki-e/cargo-llvm-cov/pull/197 :+1: > [readme example](https://github.com/taiki-e/cargo-llvm-cov#merge-coverages-generated-under-different-test-conditions) describes cargo llvm-cov clean as a command to remove artifacts. Sorry if I wasn't clear -...

@fenollp adding `--no-report` should help. In my cases, I've ended up running it once and then running the compiled binary multiple times directly during my integration tests.

@felixpis do you think you could release this separately on NPM? It doesn't look like it's going to get merged anytime soon

Please retry with `0.34.0-beta.5` and if it doesn't help, post the log from running your example with `RUST_LOG=debug`.

This is extremely strange since it looks like it's trying to use curve25519 KEX even though DH-group14-sha1 was negotiated. I'll release the latest code state as a new beta just...

Published as `v0.34.0-beta.9`

Thanks. Could you please also post a full traceback with `RUST_BACKTRACE=1`? And is the server you're connecting to publicly accessible so that I could test against it?

Are you using any specific dropbear configuration? I couldn't reproduce it with `./dropbear -F -E -R -B -p 2222` and current master branch

I'm sorry, what?