Recordscargotypenumfailure issue
Failure signature
PROJECT_COMPILE exit 101 ×1
error: could not compile `sample-typenum-integer` (bin <str>) due to 1 previous error
Evidence quality: complete · rust/rustc · compiler-diagnostic · outer cargo run · First recorded: 2026-10-22 · Last seen: 2026-10-22
sha256:7d5f70c28973…
typenum::Integer typenum::N3 typenum::NInt typenum::P5 typenum::PInt typenum::Sum typenum::U4 typenum::U7 typenum::Z0
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.
- 1.20.1 FAIL
Where it reproduced
- os=linux ×1 2026-10-22 → 2026-10-22
Nearest known PASS/FAIL boundaries
No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.
Evidence gaps
- No release in this window recorded a passing observation at PROJECT_COMPILE.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- typenum 1.20.1: typenum::Sum 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. HOWtypenum::Sum MIT-0 · 2026-10-22
- typenum 1.20.1: typenum::op 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. HOWtypenum::op MIT-0 · 2026-10-22
- typenum 1.20.1: typenum::Unsigned 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. HOWtypenum::Unsigned MIT-0 · 2026-10-22