Recordsgolanggolang.org/x/toolsfailure issue
Failure signature
PROJECT_RESOLVE exit 1 ×2
test/contract.go:<n>:<n>: missing go.sum entry for module providing package cloud.google.com/go/storage (imported by example.com/sample/test); to add: …
Evidence quality: complete · go/module · resolve-diagnostic · outer go run · First recorded: 2026-09-19 · Last seen: 2026-09-19
sha256:960c448010d3…
Where it was measured
PASS means the release recorded a passing observation at PROJECT_RESOLVE and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- v0.1.6-0.20210726203631-07bc1bf47fb2 not measured
- v0.0.0-20200825202427-b303f430e36d not measured
- v0.0.0-20200804011535-6c149bb5ef0d not measured
- v0.0.0-20200618134242-20370b0cb4b2 FAIL
- v0.0.0-20200331025713-a30bf2db82d4 not measured
- v0.0.0-20200130002326-2f3ba24bd6e7 not measured
- v0.0.0-20200103221440-774c71fcf114 not measured
Where it reproduced
- os=linux · runtime=go@1.26 ×2 2026-09-19 → 2026-09-19
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: 5 · 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 release in this window recorded a passing observation at PROJECT_RESOLVE.
- Releases in this window never measured at PROJECT_RESOLVE: 6
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.