Recordsgolanggithub.com/cespare/xxhash/v2failure issue
Failure signature
PROJECT_COMPILE exit 1 ×1
<path> cannot use prometheus.MustNewConstMetric(c.desc, prometheus.GaugeValue, c.value) (value of interface type prometheus.Metric) as *prometheus.Metric value …
Evidence quality: complete · go/compiler · compiler-diagnostic · outer go run · First recorded: 2026-08-30 · Last seen: 2026-08-30
sha256:826fe69d9410…
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-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 failing release v2.2.0 → first passing release v2.3.0
One side of this boundary has no resolved dependency tree, so nothing could be compared.
Evidence gaps
- Releases in this window never measured at PROJECT_COMPILE: 2
- No resolved dependency tree for v2.3.0 or for v2.2.0, 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
No published sample names these releases.