Recordsgolanggithub.com/cespare/xxhash/v2failure issue
Failure signature
PROJECT_TEST exit 1 ×1
--- FAIL: TestGaugeOperations (0.00s) …
Evidence quality: complete · go/test · test-runner-diagnostic · outer go test · First recorded: 2026-08-31 · Last seen: 2026-08-31
sha256:552acf21e110…
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.
- v2.3.0 PASS 303 passing observations
- v2.2.0 PASS 4 passing observations
- v2.1.2 FAIL
- v2.1.1 PASS 15 passing observations
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-08-31 → 2026-08-31
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 v2.1.1 → first failing release v2.1.2
Both trees resolved every dependency to the same version. Nothing here moved.
-
Last failing release v2.1.2 → first passing release v2.2.0
One side of this boundary has no resolved dependency tree, so nothing could be compared.
Evidence gaps
- No resolved dependency tree for v2.2.0 or for v2.1.2, so the versions either side of the boundary could not be compared.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- github.com/cespare/xxhash/v2 v2.1.2: Digest, New, Sum64 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. HOWDigestNewSum64Sum64String MIT-0 · 2026-08-28