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.

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

rt::io::signal tests are ignored #10096

Closed
alexcrichton opened this issue Oct 27, 2013 · 1 comment
Closed

rt::io::signal tests are ignored #10096

alexcrichton opened this issue Oct 27, 2013 · 1 comment
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows

Comments

@alexcrichton
Copy link
Member

If these tests are run in isolation repeatedly, they will frequently cause the stdtest executable to never exit.

This is causing deadlocks on the bots and I'm ignoring these for now.

alexcrichton added a commit to alexcrichton/rust that referenced this issue Oct 27, 2013
These tests can reliably cause the stdtest process to never exit (all uv threads
are stuck in their event loops). Ignoring these for now

cc rust-lang#10096
@alexcrichton
Copy link
Member Author

Nope, found the bug.

flip1995 pushed a commit to flip1995/rust that referenced this issue Dec 17, 2022
fix: not suggest seek_to_start_instead_of_rewind when expr is used

changelog: [`seek_to_start_instead_of_rewind`]: No longer lints, if the return of `seek` is used.
[rust-lang#10096](rust-lang/rust-clippy#10096)
<!-- changelog_checked -->

Fixes rust-lang#10065
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows
Projects
None yet
Development

No branches or pull requests

1 participant