CodeSampleX

Recordsgolanggolang.org/x/expfailure issue

Failure signature

PROJECT_COMPILE exit 1 ×1

test/contract.go:<n>:<n>: <str> imported and not used

Evidence quality: complete · go/compiler · compiler-diagnostic · outer go run · First recorded: 2026-09-03 · Last seen: 2026-09-03

sha256:d5fae02e8604…

golang.org/x/exp/mmap.Open golang.org/x/exp/mmap.ReaderAt

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

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.

Libraryv0.0.0-20260824195058-e88cd73687aav0.0.0-20251023183803-a4bb9ffd2546v0.0.0-20240506185415-9bf2ced13842v0.0.0-20230515195305-f3d0a9c9a5cc
github.com/google/go-cmp v0.6.0 v0.7.0 v0.6.0 v0.6.0
golang.org/x/mod v0.39.0 v0.37.0 v0.17.0 v0.6.0
golang.org/x/tools v0.49.0 v0.46.0 v0.21.0 v0.2.0
golang.org/x/tools/go/packages/packagestest v0.1.1-deprecated v0.1.1-deprecated — —

Moved: 3 · 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

Published answers for the affected releases

Back to the package