Recordscargoclapfailure issue
Failure signature
PROJECT_TEST exit 101 ×1
error: test failed, to rerun pass `--test contract` · running 0 tests …
Evidence quality: complete · rust/test · test-runner-diagnostic · outer cargo test · First recorded: 2026-10-22 · Last seen: 2026-10-22
sha256:a5ae8fd57d8b…
clap::Arg clap::ArgAction clap::Command
Where it was measured
PASS means the release recorded a passing observation at PROJECT_TEST and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- 4.6.7 PASS 11 passing observations
- 4.6.6 PASS 3 passing observations
- 4.6.4 FAIL
- 4.6.0 not measured
- 4.5.59 PASS 1 passing observations
Where it reproduced
- os=linux ×1 2026-10-22 → 2026-10-22
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 passing release 4.5.59 → first failing release 4.6.4
Releases between them never measured at this stage: 1
One side of this boundary has no resolved dependency tree, so nothing could be compared.
-
Last failing release 4.6.4 → first passing release 4.6.6
What differs across the boundary
- clap_builder 4.6.6 → 4.6.2 evidence
- clap_derive 4.6.4 → — hypothesis
A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.
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 | 4.6.7 | 4.6.6 | 4.6.4 | 4.6.0 |
|---|---|---|---|---|
| clap_builder | 4.6.7 | 4.6.6 | 4.6.2 | 4.6.0 |
| clap_derive | 4.6.7 | 4.6.4 | — | — |
Moved: 2 · unchanged at every release: 0
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
- Releases in this window never measured at PROJECT_TEST: 1
- No resolved dependency tree for 4.5.59 or for 4.6.4, so the versions either side of the boundary could not be compared.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- clap 4.6.4: clap::Arg 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. HOWclap::Arg MIT-0 · 2026-10-22
- clap 4.6.4: clap::Command 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. HOWclap::Command MIT-0 · 2026-10-22
- clap 4.6.4 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-22