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

Mysterious runtime deadlock #10712

Closed
alexcrichton opened this issue Nov 29, 2013 · 1 comment
Closed

Mysterious runtime deadlock #10712

alexcrichton opened this issue Nov 29, 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

I have found that this command will eventually deadlock (no schedulers making progress)

for i in {1..1000}; do; RUST_TEST_TASKS=1 ./x86_64-apple-darwin/stage2/test/stdtest-x86_64-apple-darwin multiple_connect_serial_ip6 || break; done

Still doing investigation, but wanted to open an issue on it.

@alexcrichton
Copy link
Member Author

This was my own problem, nothing to worry about.

flip1995 pushed a commit to flip1995/rust that referenced this issue May 5, 2023
…ts, r=llogiq

Document that `cargo clippy --fix` implies `--all-targets`

In [`cargo fix`'s documentation](https://doc.rust-lang.org/cargo/commands/cargo-fix.html) they indicate that `fix` implies `--all-targets` if no target is supplied. As Clippy uses Cargo under the hood, this also applies to Clippy, but we didn't document that behaviour.

This PR changes that

Fixes rust-lang#10690
changelog: Add to documentation that `--fix` implies `--all-targets`
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