Recordsgolanggolang.org/x/xerrorsfailure issue
Failure signature
PROJECT_TEST exit 1 ×1
--- FAIL: <token> (0.00s) · FAIL example.com/ednssample/test 0.004s
Evidence quality: complete · go/test · test-runner-diagnostic · outer go test · First recorded: 2026-08-30 · Last seen: 2026-08-30
sha256:36a7340bb4ef…
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.
- v0.0.0-20200804184101-5ec99f83aff1 FAIL
- v0.0.0-20191204190536-9bdfabe68543 PASS 3 passing observations
- v0.0.0-20191011141410-1b5146add898 not measured
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-08-30 → 2026-08-30
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 v0.0.0-20191204190536-9bdfabe68543 → first failing release v0.0.0-20200804184101-5ec99f83aff1
Both trees resolved every dependency to the same version. Nothing here moved.
Evidence gaps
- Releases in this window never measured at PROJECT_TEST: 1
- 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