Recordsgolanggolang.org/x/xerrorsfailure issue
Failure signature
UNKNOWN exit 1 Evidence gap ×1
# example.com/validate_rules/test …
Evidence quality: complete · go · unclassified-diagnostic · outer go run · gap stage-unknown · First recorded: 2026-10-12 · Last seen: 2026-10-12
sha256:f479d1b3c241…
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.
- v0.0.0-20200804184101-5ec99f83aff1 FAIL
- v0.0.0-20191204190536-9bdfabe68543 not measured
- v0.0.0-20191011141410-1b5146add898 not measured
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-10-12 → 2026-10-12
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: 2
- No failure domain was inferred for this failure.
Published answers for the affected releases
- golang.org/x/xerrors v0.0.0-20200804184101-5ec99f83aff1: xerrors error wrapping and chain inspection with Errorf and Is 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. HOWxerrors.Errorfxerrors.Is MIT-0 · 2026-08-27