Recordscargoh2failure issue
Failure signature
PROJECT_COMPILE exit 101 ×1
error: could not compile `test-hyper-util` (bin <str>) due to 1 previous error
Evidence quality: complete · rust/rustc · compiler-diagnostic · outer cargo run · First recorded: 2026-09-19 · Last seen: 2026-09-19
sha256:a67fd218023f…
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 ×1 2026-09-19 → 2026-09-19
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.
Dependency versions across releases
What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.
| Library | 0.4.20 | 0.4.19 |
|---|---|---|
| tokio | 1.54.0 | 1.53.1 |
| tokio-util | 0.7.20 | 0.7.19 |
| atomic-waker | 1.1.2 | 1.1.2 |
| bytes | 1.12.1 | 1.12.1 |
| fnv | 1.0.7 | 1.0.7 |
| futures-core | 0.3.34 | 0.3.34 |
| futures-sink | 0.3.34 | 0.3.34 |
| http | 1.5.0 | 1.5.0 |
| indexmap | 2.14.2 | 2.14.2 |
| slab | 0.4.12 | 0.4.12 |
| tracing | 0.1.44 | 0.1.44 |
Moved: 2 · unchanged at every release: 9
An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.
Evidence gaps
- No release in this window recorded a passing observation at PROJECT_COMPILE.
- Releases in this window never measured at PROJECT_COMPILE: 1
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.