Recordsgolanggithub.com/cespare/xxhash/v2failure issue
Failure signature
PROJECT_COMPILE exit 1 ×1
<path> declared and not used: gotAuth
Evidence quality: complete · go/compiler · compiler-diagnostic · outer go test · First recorded: 2026-09-05 · Last seen: 2026-09-05
sha256:57f8400667e3…
Where it was measured
PASS means the release recorded a passing observation at PROJECT_COMPILE 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-05 → 2026-09-05
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 failing release v2.1.1 → first passing release v2.3.0
Releases between them never measured at this stage: 2
Both trees resolved every dependency to the same version. Nothing here moved.
Evidence gaps
- Releases in this window never measured at PROJECT_COMPILE: 2
- No failure domain was inferred for this failure.
Published answers for the affected releases
- github.com/cespare/xxhash/v2 v2.1.1: xxhash.New 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. HOWxxhash.New MIT-0 · 2026-08-26
- github.com/cespare/xxhash/v2 v2.1.1: New 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. HOWNewgo 1.26 MIT-0 · 2026-08-26
- github.com/cespare/xxhash/v2 v2.1.1: Sum64String 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. HOWSum64String MIT-0 · 2026-08-26