Skip to content

Optionally allow writing to stdout in test runs #13374

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
Closed
derekchiang opened this issue Apr 7, 2014 · 1 comment · Fixed by #13706
Closed

Optionally allow writing to stdout in test runs #13374

derekchiang opened this issue Apr 7, 2014 · 1 comment · Fixed by #13706

Comments

@derekchiang
Copy link
Contributor

Currently writes to stdout are redirected when running tests. However, in some cases it could be useful to allow writing to stdout. For instance, I was writing a wrapper for a C library and got a segment fault error. This caused my test to fail abruptly, as a result of which no useful output could be seen, since stdout was captured and the test wouldn't print the logs unless it failed normally.

I was able to get around this using std::io::stdio::stdout(), but that's not ideal.
@netvl
Copy link
Contributor

netvl commented Apr 23, 2014

I agree. Sometimes I write "interactive" tests which are intended to print something to the terminal. Previously it worked, and when I was porting old code to the new compiler, it surprised me that some tests became silent. This is a very useful feature sometimes. Probably add a flag to test binary?

@alexcrichton alexcrichton mentioned this issue Apr 23, 2014
Merged
alexcrichton added a commit to alexcrichton/rust that referenced this issue Apr 24, 2014
@alexcrichton
test: Add an option to not capture output
65f68dc 
A new flag to the test runner, --nocapture, can be passed to instruct that the
output of tests should not be captured by default. The behavior can also be
triggered via a RUST_TEST_NOCAPTURE environment variable being set.

Closes rust-lang#13374
bors added a commit that referenced this issue Apr 24, 2014
@bors
auto merge of #13706 : alexcrichton/rust/test-nocapture, r=brson
3485d90 
A new flag to the test runner, --nocapture, can be passed to instruct that the
output of tests should not be captured by default. The behavior can also be
triggered via a RUST_TEST_NOCAPTURE environment variable being set.

Closes #13374
bors added a commit to rust-lang-ci/rust that referenced this issue Oct 18, 2022
@bors
Auto merge of rust-lang#13391 - dvdsk:update-manual, r=lnicola
43c7f3c 
Update manual now stable can be installed with rustup

this a new PR for rust-lang#13374 as `bors squash` seemed to have broken `bors`
_______
`rustup` can now install `rust-analyzer` for the stable tool-chain. This commit removes the note that `rustup` can only install for the nightly branch and adjusts the command.

I also added a note on how to find the path to the `rust-analyzer` binary when installed using `rustup`, and suggestions on how to work around it not being placed in `~/.cargo/bin`.

I thought it would be ideal to point everyone to use `rustup run stable rust-analyzer` to start `rust-analyzer`. That would make it trivial to switch to nightly however I could not get this to work in `nvim` therefore I left it as a suggestion at the end.
bors added a commit to rust-lang-ci/rust that referenced this issue Sep 24, 2024
@bors
Auto merge of rust-lang#13374 - cuishuang:master, r=Centri3
1e797e9 
Remove unnecessary symbols and add missing symbols

*Please write a short comment explaining your change (or "none" for internal only changes)*

changelog: Remove unnecessary symbols and add missing symbols
@epage epage mentioned this issue Apr 11, 2025
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

test: Add an option to not capture output alexcrichton/rust
2 participants
@netvl @derekchiang