Recordsgolanggithub.com/pkg/errorsfailure issue
Failure signature
PROJECT_TEST exit 1 ×1
--- FAIL: TestAlphanumeric (0.00s) · panic: runtime error: makeslice: len out of range [recovered, repanicked] · goroutine 7 [running]: …
Evidence quality: complete · go/test · test-runner-diagnostic · outer go test · First recorded: 2026-09-02 · Last seen: 2026-09-02
sha256:1f9f709cab3e…
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.
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-09-02 → 2026-09-02
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.8.1 → first failing release v0.9.1
Both trees resolved every dependency to the same version. Nothing here moved.
Evidence gaps
- No failure domain was inferred for this failure.
Published answers for the affected releases
- github.com/pkg/errors v0.9.1: Errorf 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. HOWgithub.com/pkg/errors.Errorf MIT-0 · 2026-09-06
- github.com/pkg/errors v0.9.1: Wrapf 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. HOWgithub.com/pkg/errors.Wrapf MIT-0 · 2026-09-06
- github.com/pkg/errors v0.9.1: Wrap 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. HOWgithub.com/pkg/errors.Wrap MIT-0 · 2026-09-06