This repository has been archived by the owner on Dec 29, 2021. It is now read-only.
main_binary's stderr may include extra text
#79
Comments
|
See #51 for a discussion on alternative ways of finding the test binary. One workaround for this issue is to serialize the tests. This gets annoying for random contributors because they won't know of the requirement. One workaround is requires more advanced stderr matching for clients to choose to detect and ignore this text. |
|
Should cargo printing this despite |
epage
added a commit
to epage/assert_cli
that referenced
this issue
May 25, 2018
This switches us from using `cargo run` to `cargo build`, reading where the binary is placed, and callin that instead. Fixes assert-rs#95 because the user changing the `CWD` doesn't impact `cargo build`. Fixes assert-rs#79 because there is no `cargo` output when capturing the user's stdout/stderr. Fixes assert-rs#51 because the user changing the environment doesn't impact `cargo build`. This is a step towards working around assert-rs#100 because we can allow a user to cache the result of `cargo build`.
|
Addressed in assert_cmd |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
assert_cliversion: 0.5.4By default,
cargo testruns tests in parallel. When two tests invokemain_binaryin parallel, cargo will block until the other instance of cargo is finished.Unfortunately, it seems that cargo prints
Blocking waiting for file lock on build directoryto stderr, even with--quiet, or at least that is what I'm assuming is going wrong in cobalt-org/cobalt.rs#352The text was updated successfully, but these errors were encountered: