Skip to content

Duplicated error messages on cargo test. #54138

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

Closed
dpc opened this issue Sep 11, 2018 · 2 comments
Closed

Duplicated error messages on cargo test. #54138

dpc opened this issue Sep 11, 2018 · 2 comments

Comments

@dpc
Copy link
Contributor

dpc commented Sep 11, 2018

Why am I getting same error twice?

[nix-shell:~/lab/crev]$ cargo test
   Compiling crev-lib v0.0.1 (file:///home/dpc/lab/crev/crev-lib)                                                                   
error[E0425]: cannot find function `f` in this scope
   --> crev-lib/src/repo/mod.rs:150:9
    |
150 |         f();
    |         ^ not found in this scope

error[E0425]: cannot find function `f` in this scope
   --> crev-lib/src/repo/mod.rs:150:9
    |
150 |         f();
    |         ^ not found in this scope

error: aborting due to previous error

For more information about this error, try `rustc --explain E0425`.
error: Could not compile `crev-lib`.
warning: build failed, waiting for other jobs to finish...
error: aborting due to previous error

For more information about this error, try `rustc --explain E0425`.
error: Could not compile `crev-lib`.

To learn more, run the command again with --verbose.

[nix-shell:~/lab/crev]$ rustc --version
rustc 1.30.0-nightly (551244f05 2018-09-10)

In case it might be project-specific, you can download https://github.com/dpc/crev

@cuviper
Copy link
Member

cuviper commented Sep 11, 2018

If you use --verbose, you'll see the rustc commands. Most likely this is the library being built normally and with unit tests at the same time, adding --test for the latter.

@estebank
Copy link
Contributor

This is rust-lang/cargo#5128 running rustc twice. It needs to be fixed.

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