Recordsgolanggolang.org/x/toolsfailure issue
Failure signature
PROCESS_START process start failed Evidence gap ×3
Evidence quality: partial · structured-termination · gap diagnostic-missing · First recorded: 2026-08-30 · Last seen: 2026-09-19
sha256:c12549970456…
Where it was measured
PASS means the release recorded a passing observation at PROCESS_START and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- v0.43.0 not measured
- v0.40.0 not measured
- v0.36.0 FAIL
- v0.31.0 FAIL
- v0.22.0 not measured
- v0.14.0 not measured
- v0.0.0-20190425150028-36563e24a262 not measured
- v0.0.0-20190311212946-11955173bddd not measured
- v0.0.0-20190226205152-f727befe758c FAIL
Where it reproduced
- executionContext=node · moduleSystem=cjs · os=linux · runtime=node@22.23 ×1 2026-08-31 → 2026-08-31
- executionContext=node · moduleSystem=esm · os=linux · runtime=node@22.23 ×1 2026-08-30 → 2026-08-30
- 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.31.0 | v0.22.0 | v0.14.0 | v0.0.0-20190425150028-36563e24a262 | v0.0.0-20190311212946-11955173bddd | v0.0.0-20190226205152-f727befe758c |
|---|---|---|---|---|---|---|
| golang.org/x/mod | v0.24.0 | v0.18.0 | v0.13.0 | — | — | — |
| golang.org/x/net | v0.38.0 | v0.31.0 | v0.17.0 | v0.0.0-20190311183353-d8887717615a | v0.0.0-20190311183353-d8887717615a | v0.0.0-20190213061140-3a22650c66bd |
| golang.org/x/sync | v0.12.0 | v0.7.0 | v0.4.0 | v0.0.0-20190423024810-112230192c58 | — | — |
| github.com/google/go-cmp | v0.6.0 | v0.6.0 | — | — | — | — |
| github.com/yuin/goldmark | — | v1.4.13 | v1.4.13 | — | — | — |
| golang.org/x/sys | — | — | v0.14.0 | — | — | — |
| golang.org/x/telemetry | — | v0.0.0-20240521205824-bda55230c457 | — | — | — | — |
| google.golang.org/appengine | — | — | — | — | — | v1.4.0 |
Moved: 3 · unchanged at every release: 5
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
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- The captured output could not establish: diagnostic-missing.
- No release in this window recorded a passing observation at PROCESS_START.
- Releases in this window never measured at PROCESS_START: 6
- No failure domain was inferred for this failure.
Published answers for the affected releases
- golang.org/x/tools v0.31.0: imports.Process 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. HOWgolang.org/x/tools/imports.Processgo 1.26.6 MIT-0 · 2026-08-30
- golang.org/x/tools v0.31.0: inspector.New 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. HOWgolang.org/x/tools/go/ast/inspector.New MIT-0 · 2026-08-29
- golang.org/x/tools v0.31.0: txtar.Parse 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. HOWgolang.org/x/tools/txtar.Parse MIT-0 · 2026-08-27