Recordscargor-efifailure issue
Failure signature
UNKNOWN exit 101 Evidence gap ×1
Compiling sample-r-efi v0.1.0 (<path> · Finished `dev` profile [unoptimized + debuginfo] target(s) in 0.57s · Running `target/debug/sample-r-efi` …
Evidence quality: complete · cargo · unclassified-diagnostic · outer cargo run · gap stage-unknown · First recorded: 2026-10-13 · Last seen: 2026-10-13
sha256:b9a0fe86cd4b…
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-10-13 → 2026-10-13
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.
- Releases in this window never measured at UNKNOWN: 1
- No failure domain was inferred for this failure.
Published answers for the affected releases
- r-efi 6.0.0: r_efi 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. HOWr_efi MIT-0 · 2026-10-13
- r-efi 6.0.0 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-13