Recordscargoserde_corefailure issue
Failure signature
UNKNOWN exit 101 Evidence gap ×1
Compiling sample-serde-core v1.0.0 (<path> · Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.27s · Running `target/debug/contract` …
Evidence quality: complete · cargo · unclassified-diagnostic · outer cargo run · gap stage-unknown · First recorded: 2026-09-14 · Last seen: 2026-09-14
sha256:eeb9864183a6…
serde_core
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.
- 1.0.229 FAIL
Where it reproduced
- os=linux ×1 2026-09-14 → 2026-09-14
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
- 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.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- serde_core 1.0.229 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-09-14