Recordsgolanggithub.com/google/go-cmpfailure issue
Failure signature
UNKNOWN exit 1 Evidence gap ×1
panic: ambiguous set of applicable options at {string}: · Transformer(Trim, strings.TrimSpace) · Comparer(main.verifyCmpDiff.func2) …
Evidence quality: complete · go · unclassified-diagnostic · outer go run · gap stage-unknown · First recorded: 2026-10-16 · Last seen: 2026-10-16
sha256:2e190e692db4…
github.com/google/go-cmp/cmp.AllowUnexported github.com/google/go-cmp/cmp.Comparer github.com/google/go-cmp/cmp.Diff github.com/google/go-cmp/cmp.Transformer github.com/google/go-cmp/cmp/cmpopts.IgnoreFields github.com/google/go-cmp/cmp/cmpopts.SortSlices
Where it was measured
PASS means the release recorded a passing observation at UNKNOWN and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- v0.5.9 not measured
- v0.5.5 not measured
- v0.5.4 not measured
- v0.5.1 FAIL
- v0.5.0 not measured
- v0.4.1 not measured
- v0.4.0 not measured
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-10-16 → 2026-10-16
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.5.9 | v0.5.5 | v0.5.4 | v0.5.1 | v0.5.0 | v0.4.1 | v0.4.0 |
|---|---|---|---|---|---|---|---|
| golang.org/x/xerrors | — | v0.0.0-20200804184101-5ec99f83aff1 | v0.0.0-20191204190536-9bdfabe68543 | v0.0.0-20191204190536-9bdfabe68543 | v0.0.0-20191204190536-9bdfabe68543 | v0.0.0-20191204190536-9bdfabe68543 | 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
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- The captured output could not establish: stage-unknown.
- No release in this window recorded a passing observation at UNKNOWN.
- Releases in this window never measured at UNKNOWN: 6
- No failure domain was inferred for this failure.
Published answers for the affected releases
- github.com/google/go-cmp v0.5.1: cmpopts.SortSlices 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/cmpopts.SortSlices MIT-0 · 2026-10-16
- github.com/google/go-cmp v0.5.1: cmp.Equal 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.Equal MIT-0 · 2026-10-16
- github.com/google/go-cmp v0.5.1: cmp.Diff 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.Diff MIT-0 · 2026-10-16