Recordscargofutures-macrofailure issue
Failure signature
PROJECT_COMPILE exit 101 ×1
error: could not compile `sample` (lib) due to 5 previous errors · error: could not compile `sample` (lib test) due to 5 previous errors
Evidence quality: complete · rust/rustc · compiler-diagnostic · outer cargo test · First recorded: 2026-10-31 · Last seen: 2026-10-31
sha256:af4b7ff706d4…
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.
- 0.3.34 FAIL
Where it reproduced
- os=linux ×1 2026-10-31 → 2026-10-31
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
- futures-macro 0.3.34 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-10-31