Recordsgolanggolang.org/x/toolsfailure issue
Failure signature
PROJECT_TEST exit 1 ×1
--- FAIL: TestNew_DefaultFields (0.00s) · contract_test.go:<n>: expected default CertSelection to be non-nil …
Evidence quality: complete · go/test · test-runner-diagnostic · outer go test · First recorded: 2026-08-31 · Last seen: 2026-08-31
sha256:7e9d088c5c85…
Where it was measured
PASS means the release recorded a passing observation at PROJECT_TEST 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 PASS 1 passing observations
- v0.36.0 not measured
- v0.31.0 FAIL
- v0.22.0 PASS 8 passing observations
- v0.14.0 PASS 1 passing observations
- v0.13.0 not measured
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-08-31 → 2026-08-31
Nearest known PASS/FAIL boundaries
The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.
-
Last passing release v0.22.0 → first failing release v0.31.0
What differs across the boundary
- github.com/yuin/goldmark v1.4.13 → — hypothesis
- golang.org/x/mod v0.18.0 → v0.24.0 hypothesis
- golang.org/x/net v0.31.0 → v0.38.0 hypothesis
- golang.org/x/sync v0.7.0 → v0.12.0 hypothesis
- golang.org/x/telemetry v0.0.0-20240521205824-bda55230c457 → — hypothesis
A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.
-
Last failing release v0.31.0 → first passing release v0.40.0
Releases between them never measured at this stage: 1
One side of this boundary has no resolved dependency tree, so nothing could be compared.
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: 3 · unchanged at every release: 4
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
- Releases in this window never measured at PROJECT_TEST: 3
- No resolved dependency tree for v0.40.0 or for v0.31.0, so the versions either side of the boundary could not be compared.
- 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