CodeSampleX

Recordsgolanggithub.com/google/go-cmpfailure issue

Failure signature

UNKNOWN exit 1 Evidence gap ×1

FAIL: expected diff output to contain .Timestamp, got: structfieldcmp.AuditRecord{ · ID: <str>, · - Timestamp: 1700000000, · + Timestamp: 1700000999,

Evidence quality: complete · go · unclassified-diagnostic · outer go run · gap stage-unknown · First recorded: 2026-09-15 · Last seen: 2026-09-15

sha256:91f55331fa53…

github.com/google/go-cmp/cmp.Diff github.com/google/go-cmp/cmp.Equal 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.StructField

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.

Where it reproduced

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.

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

Published answers for the affected releases

Back to the package