Recordsgolanggolang.org/x/expfailure issue
Failure signature
PROJECT_COMPILE exit 1 ×1
<path> cannot use errNode (variable of type *antlr.ErrorNodeImpl) as antlr.Token value in argument to rootCtx.AddErrorNode: *antlr.ErrorNodeImpl does not …
Evidence quality: complete · go/compiler · compiler-diagnostic · outer go test · First recorded: 2026-08-30 · Last seen: 2026-08-30
sha256:feee914ca805…
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.
- v0.0.0-20260824195058-e88cd73687aa not measured
- v0.0.0-20251023183803-a4bb9ffd2546 not measured
- v0.0.0-20240506185415-9bf2ced13842 FAIL
- v0.0.0-20230515195305-f3d0a9c9a5cc not measured
- v0.0.0-20200224162631-6cc2880d07d6 not measured
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-08-30 → 2026-08-30
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-20260824195058-e88cd73687aa | v0.0.0-20251023183803-a4bb9ffd2546 | v0.0.0-20240506185415-9bf2ced13842 | v0.0.0-20230515195305-f3d0a9c9a5cc | v0.0.0-20200224162631-6cc2880d07d6 |
|---|---|---|---|---|---|
| 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 | v0.2.0 |
| golang.org/x/tools | v0.49.0 | v0.46.0 | 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 |
| 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/tools/go/packages/packagestest | v0.1.1-deprecated | v0.1.1-deprecated | — | — | — |
| golang.org/x/xerrors | — | — | — | — | v0.0.0-20200804184101-5ec99f83aff1 |
Moved: 3 · 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_COMPILE.
- Releases in this window never measured at PROJECT_COMPILE: 4
- No failure domain was inferred for this failure.
Published answers for the affected releases
- golang.org/x/exp v0.0.0-20240506185415-9bf2ced13842 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. HOWgo 1.26.6 MIT-0 · 2026-08-23