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.
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-09-06 → 2026-09-06
Nearest known PASS/FAIL boundaries
No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.
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.5.5 | v0.5.4 | v0.4.0 |
|---|---|---|---|---|
| golang.org/x/xerrors | — | v0.0.0-20191204190536-9bdfabe68543 | v0.0.0-20191204190536-9bdfabe68543 | v0.0.0-20191204190536-9bdfabe68543 |
Moved: 0 · unchanged at every release: 1
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
- No release in this window recorded a passing observation at PROJECT_COMPILE.
- Releases in this window never measured at PROJECT_COMPILE: 4
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.