Recordscargolibcfailure issue
Failure signature
PROJECT_COMPILE exit 101 E0631 ×2
error[E0631]: type mismatch in closure arguments
Evidence quality: complete · rust/rustc · compiler-diagnostic · outer cargo run · First recorded: 2026-09-19 · Last seen: 2026-11-01
sha256:08581f58869b…
Where it was measured
PASS means the release recorded a passing observation at PROJECT_COMPILE and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
Where it reproduced
- os=linux ×2 2026-09-19 → 2026-11-01
Nearest known PASS/FAIL boundaries
The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.
-
Last failing release 0.2.189 → first passing release 0.2.190
Both trees resolved every dependency to the same version. Nothing here moved.
-
Last passing release 0.2.190 → first failing release 0.2.191
Both trees resolved every dependency to the same version. Nothing here moved.
Evidence gaps
- No failure domain was inferred for this failure.
Published answers for the affected releases
- libc 0.2.189: libc This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWlibc MIT-0 · 2026-09-17
- libc 0.2.189 This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOW MIT-0 · 2026-09-14