Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

duplicate output #1023

Closed
kevinburke opened this issue Dec 9, 2014 · 3 comments
Closed

duplicate output #1023

kevinburke opened this issue Dec 9, 2014 · 3 comments

Comments

@kevinburke
Copy link

When I run cargo test the compiler prints errors twice. I'm not sure if this is an error in the compiler or in cargo.

$ cargo test
   Compiling rustclient v0.0.1 (file:///Users/kevin/code/rustclient)
/Users/kevin/code/rustclient/src/lib.rs:163:26: 163:44 error: mismatched types: expected `char`, found `&[u8]` (expected char, found &-ptr)
/Users/kevin/code/rustclient/src/lib.rs:163         request_buf.push(topline.as_bytes());
                                                                     ^~~~~~~~~~~~~~~~~~
/Users/kevin/code/rustclient/src/lib.rs:163:26: 163:44 error: mismatched types: expected `char`, found `&[u8]` (expected char, found &-ptr)
/Users/kevin/code/rustclient/src/lib.rs:163         request_buf.push(topline.as_bytes());
                                                                     ^~~~~~~~~~~~~~~~~~
error: aborting due to previous error
error: aborting due to previous error
$ cargo --version
cargo 0.0.1-pre-nightly (0f6667c 2014-12-08 21:19:01 +0000)
@steveklabnik
Copy link
Member

I'm seeing this too, with errors specifically.

@alexcrichton
Copy link
Member

This a dupe of #851, specifically your crate is being compiled with and without --test in parallel, note that the version without --test will be used for doctests.

@kevinburke
Copy link
Author

I guess I'm not seeing any good responses in that thread for how to fix the issue. I tried running cargo test -j1 but I got the same duplicate output problem. I also tried running rustc src/lib.rs but it failed when trying to load the external dependency.

I'm sure there's some reason why there's duplicate output, it just feels weird and unintuitive that the default test runner "cargo test" would cause issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants