Recordsgolanggithub.com/google/go-cmpfailure issue
Failure signature
PROJECT_COMPILE exit 1 ×1
test/contract.go:<n>:<n>: <str> imported and not used · test/contract.go:<n>:<n>: <str> imported and not used …
Evidence quality: complete · go/compiler · compiler-diagnostic · outer go run · First recorded: 2026-09-06 · Last seen: 2026-09-06
sha256:17537f9fa97a…
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.
- v0.7.0 not measured
- v0.6.0 PASS 1 passing observations
- v0.5.9 FAIL
- v0.5.7 PASS 7 passing observations
- v0.5.6 not measured
- v0.5.5 not measured
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-09-06 → 2026-09-06
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.5.7 → first failing release v0.5.9
What differs across the boundary
- golang.org/x/xerrors v0.0.0-20191204190536-9bdfabe68543 → — hypothesis
A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.
-
Last failing release v0.5.9 → first passing release v0.6.0
Both trees resolved every dependency to the same version. Nothing here moved.
Dependency versions across releases
What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.
| Library | v0.7.0 | v0.6.0 | v0.5.9 | v0.5.7 | v0.5.6 | v0.5.5 |
|---|---|---|---|---|---|---|
| golang.org/x/xerrors | — | — | — | v0.0.0-20191204190536-9bdfabe68543 | v0.0.0-20191204190536-9bdfabe68543 | v0.0.0-20200804184101-5ec99f83aff1 |
Moved: 1 · unchanged at every release: 0
An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.
Evidence gaps
- Releases in this window never measured at PROJECT_COMPILE: 3
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.