Recordscargoccfailure issue
Failure signature
UNKNOWN exit 101 Evidence gap ×1
Compiling sample-ring-digest v1.0.0 (<path> · Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.18s · Running `target/debug/contract` …
Evidence quality: complete · cargo · unclassified-diagnostic · outer cargo run · gap stage-unknown · First recorded: 2026-09-20 · Last seen: 2026-09-20
sha256:58d2cf0f1acc…
Where it was measured
PASS means the release recorded a passing observation at UNKNOWN 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-20 → 2026-09-20
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 | 1.6.0 | 1.4.7 | 1.4.6 | 1.4.3 | 1.4.0 |
|---|---|---|---|---|---|
| find-msvc-tools | 0.1.14 | 0.1.13 | 0.1.12 | 0.1.12 | 0.1.9 |
| jobserver | — | — | — | 0.1.35 | 0.1.35 |
| libc | — | — | — | 0.2.189 | 0.2.189 |
| shlex | 2.0.1 | 2.0.1 | 2.0.1 | 2.0.1 | 2.0.1 |
Moved: 1 · unchanged at every release: 3
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
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- The captured output could not establish: stage-unknown.
- No release in this window recorded a passing observation at UNKNOWN.
- Releases in this window never measured at UNKNOWN: 4
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.