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 }}
CI flake: Check smoketests/mod.rs is complete #6555
Exact job 127995362017, run 42248020884, attempt 1: cargo ci smoketests check-mod-list failed before the module-list check could run.
Primary diagnostic: sccache: error: Connection to server timed out: Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }. The compiler wrapper exited 2 while compiling libc's build script; Cargo's could not compile libc / exit 101 is downstream. Why the cache server was unavailable is unproven; this is not evidence of a libc or smoketest correctness bug.
Reviewed all 998 Test flakes project items, including 101 OPEN issues across repositories, and searched organization-wide OPEN issues for sccache and Connection refused.
Selected OPEN #6405: its exact failed log has the same sccache ConnectionRefused diagnostic, libc build-script wrapper exit 2, and Cargo exit 101. Different triggering commands do not distinguish this cache-server failure. Its open-root timeline already had 4 distinct canonical duplicate sources; no closed issues were inspected to reconstruct history.
No title/team operations are applicable to duplicate closure. No root, label, assignee, or project-field edits were made; all other triage changes remain DRY RUN.
Activity
clockwork-labs-bot commentedon Nov 11, 2026
Symptoms and root cause
42248020884, attempt 1:cargo ci smoketests check-mod-listfailed before the module-list check could run.sccache: error: Connection to server timed out: Os { code: 111, kind: ConnectionRefused, message: "Connection refused" }. The compiler wrapper exited 2 while compilinglibc's build script; Cargo'scould not compile libc/ exit 101 is downstream. Why the cache server was unavailable is unproven; this is not evidence of a libc or smoketest correctness bug.Duplicate selection
sccacheandConnection refused.ConnectionRefuseddiagnostic, libc build-script wrapper exit 2, and Cargo exit 101. Different triggering commands do not distinguish this cache-server failure. Its open-root timeline already had 4 distinct canonical duplicate sources; no closed issues were inspected to reconstruct history.cache storage failed to read: Unexpected (temporary) at read => send http request#5557 instead establishes a cache-backend DNS lookup failure during server startup, absent here; the direct match to CI flake - sccache server connection refused #6405 is stronger.Proposed operations
CLOSED, reasonDUPLICATE, andduplicateOfpointing to CI flake - sccache server connection refused #6405; the root remains OPEN.