Skip to content

Capturing stdout/stderr in custom test harnesses #8

New issue

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

#

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

Already on GitHub? # to your account

Jump to bottom
Open
Tracked by #2
epage opened this issue May 10, 2024 · 3 comments
Open
Tracked by #2

Capturing stdout/stderr in custom test harnesses #8

epage opened this issue May 10, 2024 · 3 comments
Labels
S-needs-team-input Status: Needs input from team on whether/how to proceed.

Comments

@epage
Copy link

epage commented May 10, 2024

No description provided.

@epage epage added the S-needs-team-input Status: Needs input from team on whether/how to proceed. label May 10, 2024
@epage
Copy link
Author

epage commented May 10, 2024

rust-lang/rfcs#3632 seems like it has potential to unbloick this

@epage epage mentioned this issue May 10, 2024
Open
7 tasks
@epage
Copy link
Author

epage commented May 14, 2024

Mara also spoke about a way to inherit TLS across threads. We'll need to follow up on it.

@epage epage mentioned this issue May 19, 2024
Merged
@epage
Copy link
Author

epage commented May 22, 2024

rust-lang/rfcs#3642 is up which solves the thread-spawning issue. This can also be used to store some test state (like test name)

# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
S-needs-team-input Status: Needs input from team on whether/how to proceed.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@epage