Conversation
|
Some changes occurred in src/tools/clippy. cc @rust-lang/clippy |
|
(rust-highfive has picked a reviewer for you, use r? to override) |
|
@bors r+ rollup=never |
|
📌 Commit f3b8812 has been approved by |
|
⌛ Testing commit f3b8812 with merge e13ae63f3c6e557d14bf14337f1b8675a5351b03... |
|
💥 Test timed out |
|
Odd, CI passed everywhere else, including the equivalent mingw runners. |
|
There were several different issues with MSVC CI recently, worth retrying. |
|
One more of #92883 (comment) |
|
@bors retry |
|
☀️ Test successful - checks-actions |
|
Finished benchmarking commit (42852d7): comparison url. Summary: This benchmark run did not return any relevant changes. If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf. @rustbot label: -perf-regression |
Update rayon and rustc-rayon This updates rayon for various tools and rustc-rayon for the compiler's parallel mode. - rayon v1.3.1 -> v1.5.1 - rayon-core v1.7.1 -> v1.9.1 - rustc-rayon v0.3.1 -> v0.3.2 - rustc-rayon-core v0.3.1 -> v0.3.2 ... and indirectly, this updates all of crossbeam-* to their latest versions. Fixes rust-lang#92677 by removing crossbeam-queue, but there's still a lingering question about how tidy discovers "runtime" dependencies. None of this is truly in the standard library's dependency tree at all.
This updates rayon for various tools and rustc-rayon for the compiler's parallel mode.
... and indirectly, this updates all of crossbeam-* to their latest versions.
Fixes #92677 by removing crossbeam-queue, but there's still a lingering question about how tidy discovers "runtime" dependencies. None of this is truly in the standard library's dependency tree at all.