Recordsgolanggolang.org/x/expfailure issue
Failure signature
PROJECT_RESOLVE exit 1 ×1
<path>:<n>:<n>: missing go.sum entry for module providing package golang.org/x/net/context (imported by google.golang.<token>); to add: …
Evidence quality: complete · go/module · resolve-diagnostic · outer go list · First recorded: 2026-09-19 · Last seen: 2026-09-19
sha256:7403329615b2…
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.0.0-20240506185415-9bf2ced13842 not measured
- v0.0.0-20230515195305-f3d0a9c9a5cc not measured
- v0.0.0-20200224162631-6cc2880d07d6 not measured
- v0.0.0-20190121172915-509febef88a4 FAIL
- v0.0.0-20181106170214-d68db9428509 not measured
Where it reproduced
- os=linux · runtime=go@1.26 ×1 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.
| Library | v0.0.0-20240506185415-9bf2ced13842 | v0.0.0-20230515195305-f3d0a9c9a5cc | v0.0.0-20200224162631-6cc2880d07d6 |
|---|---|---|---|
| golang.org/x/mod | v0.17.0 | v0.6.0 | v0.2.0 |
| golang.org/x/tools | v0.21.0 | v0.2.0 | v0.0.0-20200825202427-b303f430e36d |
| dmitri.shuralyov.com/gpu/mtl | — | — | v0.0.0-20190408044501-666a987793e9 |
| github.com/BurntSushi/xgb | — | — | v0.0.0-20160522181843-27f122750802 |
| github.com/go-gl/glfw/v3.3/glfw | — | — | v0.0.0-20200222043503-6f7a984d4dc4 |
| github.com/google/go-cmp | v0.6.0 | v0.6.0 | — |
| golang.org/x/image | — | — | v0.0.0-20190802002840-cff245a6509b |
| golang.org/x/mobile | — | — | v0.0.0-20190719004257-d2bd2a29d028 |
| golang.org/x/sys | — | — | v0.47.0 |
| golang.org/x/xerrors | — | — | v0.0.0-20200804184101-5ec99f83aff1 |
Moved: 2 · unchanged at every release: 8
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: 4
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.