Recordsgolanggithub.com/google/go-cmpfailure issue
Failure signature
PROJECT_TEST exit 1 ×2
--- FAIL: TestPathContract (0.00s) · FAIL example.com/sample 0.003s
Evidence quality: complete · go/test · test-runner-diagnostic · outer go test · First recorded: 2026-09-15 · Last seen: 2026-09-15
sha256:578ba2cc38c6…
github.com/google/go-cmp/cmp.FilterPath github.com/google/go-cmp/cmp.Ignore github.com/google/go-cmp/cmp.Option github.com/google/go-cmp/cmp.Path github.com/google/go-cmp/cmp.PathStep github.com/google/go-cmp/cmp.StructField
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.
- v0.7.0 PASS 16 passing observations
- v0.6.0 FAIL
- v0.5.9 PASS 8 passing observations
- v0.5.5 PASS 4 passing observations
- v0.5.4 PASS 4 passing observations
Where it reproduced
- os=linux · runtime=go@1.26 ×2 2026-09-15 → 2026-09-15
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.9 → first failing release v0.6.0
Both trees resolved every dependency to the same version. Nothing here moved.
-
Last failing release v0.6.0 → first passing release v0.7.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.5 | v0.5.4 |
|---|---|---|---|---|---|
| golang.org/x/xerrors | — | — | — | v0.0.0-20200804184101-5ec99f83aff1 | v0.0.0-20191204190536-9bdfabe68543 |
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
- No failure domain was inferred for this failure.
Published answers for the affected releases
- github.com/google/go-cmp v0.6.0: cmp.Options 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. HOWgithub.com/google/go-cmp/cmp.Options MIT-0 · 2026-09-15
- github.com/google/go-cmp v0.6.0: cmp.StructField 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. HOWgithub.com/google/go-cmp/cmp.StructField MIT-0 · 2026-09-15
- github.com/google/go-cmp v0.6.0: cmp.Path 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. HOWgithub.com/google/go-cmp/cmp.Path MIT-0 · 2026-09-15