You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Windows Clippy exhausts its job timeout after slow Rust setup #3134
The check annotation establishes that this cancellation was a job timeout:
The job has exceeded the maximum execution time of 15m0s
Toolchain setup logged:
00:27:01 info: syncing channel updates for 1.100.0-x86_64-pc-windows-msvc
00:27:01 info: downloading 6 components
00:40:43 warn: the missing active toolchain `1.100.0-x86_64-pc-windows-msvc` has been auto-installed
00:40:43 info: component clippy is up to date
Cache restoration followed, and Clippy ran from 00:41:36 until cancellation at 00:42:08. This is independent of the failed test shards.
.github/workflows/check-lint.yml sets timeout-minutes: 15 and invokes rustup component add clippy before restoring the Cargo workspace cache. The exact base revision's Windows Clippy job passed, with Rust setup taking 89 seconds: https://github.com/astral-sh/uv/actions/runs/44177011140/job/134371280495. The triggering astral-sh#23240 changes only Pyodide download metadata, supporting an unrelated intermittent setup delay. The logs do not establish whether downloads, installation, or runner performance caused the delay.
Investigate the provisioning delay and improve setup diagnostics or toolchain caching/preinstallation so fresh Rust setup does not consume the lint job's budget.
Related: #2907 describes slow Rust setup exhausting a macOS build deadline, but a shared cause is unconfirmed. #410 concerns explicit Rust download connection errors, which are absent here. The same attempt separately reproduced the PyPy timeout tracked by #2049 and wheel-cache timeout samples recorded in #2048; existing mitigations include astral-sh#22664 and #1907.
Activity