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.

Sign up for GitHub

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

Jump to bottom

cargo test --doc --no-run seems to be no-op. #5242

Closed
vi opened this issue Mar 25, 2018 · 1 comment · Fixed by #6628
Closed

cargo test --doc --no-run seems to be no-op. #5242

vi opened this issue Mar 25, 2018 · 1 comment · Fixed by #6628
Assignees
@dwijnand
Labels
Command-test

Comments

@vi
Copy link
Contributor

vi commented Mar 25, 2018

Expectation: check only compilability of doctests.
Reality: Finished dev [unoptimized + debuginfo] target(s) in 0.0 secs
@asoderman
Copy link

I don't believe there is a way to --no-run doctests. Running rustdoc --test --test-args no-run filters the doctests out.

This would first need to be implemented in rustdoc then cargo will need to implement doctest compilation before exiting when using --no-run.

Please correct me if I'm wrong.

@jonhoo jonhoo mentioned this issue Dec 12, 2018
Open
@dwijnand dwijnand mentioned this issue Feb 4, 2019
Merged
@dwijnand dwijnand self-assigned this Feb 4, 2019
bors added a commit that referenced this issue Feb 4, 2019
@bors
Auto merge of #6628 - dwijnand:doc-no-run, r=Eh2406
f7ba714 
Bail when trying to run "test --doc --no-run"

Fixes #5242
@bors bors closed this as completed in #6628 Feb 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dwijnand dwijnand

Labels
Command-test
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Bail when trying to run "test --doc --no-run" dwijnand/cargo
4 participants
@alexcrichton @vi @dwijnand @asoderman