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

libtest captures stdout&stderr only on first thread. #31983

Closed
dpc opened this issue Mar 1, 2016 · 1 comment
Closed

libtest captures stdout&stderr only on first thread. #31983

dpc opened this issue Mar 1, 2016 · 1 comment
Labels
A-libtest Area: `#[test]` / the `test` library C-bug Category: This is a bug. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.

Comments

@dpc
Copy link
Contributor

dpc commented Mar 1, 2016

Hi,

When testing anything multithreaded, the output of non-first thread are directly printed on the console.

I wonder if libtest could maybe expose the set_panic and set_print handlers, so other spawned threads can installed it manually as a workaround.
@NoraCodes NoraCodes mentioned this issue Mar 6, 2017
Closed
@steveklabnik steveklabnik added T-libs-api Relevant to the library API team, which will review and decide on the PR/issue. and removed A-libs labels Mar 24, 2017
@Mark-Simulacrum Mark-Simulacrum added the A-libtest Area: `#[test]` / the `test` library label Jun 20, 2017
@Mark-Simulacrum Mark-Simulacrum added the C-bug Category: This is a bug. label Jul 24, 2017
@azriel91 azriel91 mentioned this issue Dec 25, 2017
Closed
CAD97 added a commit to CAD97/rust that referenced this issue May 5, 2018
@CAD97
Reusable handle to thread-local replaceable stdout/err
db999dc 
Lays the groundwork for mitigating:
- rust-lang#12309
- rust-lang#31983
- rust-lang#40298
- rust-lang#42474
@CAD97 CAD97 mentioned this issue May 5, 2018
Closed
@Mark-Simulacrum
Copy link
Member

Closing as duplicate of #42474.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-libtest Area: `#[test]` / the `test` library C-bug Category: This is a bug. T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@dpc @steveklabnik @Mark-Simulacrum