Recordsgolanggolang.org/x/toolsfailure issue
Failure signature
UNKNOWN exit 1 Evidence gap ×1
Contract test failed: expected error on invalid Go syntax, got nil · exit status 1
Evidence quality: complete · go · unclassified-diagnostic · outer go run · gap stage-unknown · First recorded: 2026-09-15 · Last seen: 2026-09-15
sha256:b78c388f6301…
Where it was measured
PASS means the release recorded a passing observation at UNKNOWN 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-20190823170909-c4a336ef6a2f not measured
- v0.0.0-20190621195816-6e04913cbbac not measured
- v0.0.0-20190425163242-31fd60d6bfdc not measured
- v0.0.0-20190311212946-11955173bddd FAIL
- v0.0.0-20190226205152-f727befe758c not measured
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-09-15 → 2026-09-15
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-20190823170909-c4a336ef6a2f | v0.0.0-20190621195816-6e04913cbbac | v0.0.0-20190425163242-31fd60d6bfdc | v0.0.0-20190311212946-11955173bddd | v0.0.0-20190226205152-f727befe758c |
|---|---|---|---|---|---|
| golang.org/x/net | v0.0.0-20210226172049-e18ecbb05110 | v0.0.0-20190404232315-eb5bcb51f2a3 | v0.0.0-20190311183353-d8887717615a | v0.0.0-20190311183353-d8887717615a | v0.0.0-20190213061140-3a22650c66bd |
| golang.org/x/sync | v0.0.0-20190423024810-112230192c58 | v0.0.0-20190423024810-112230192c58 | v0.0.0-20190423024810-112230192c58 | — | — |
| golang.org/x/xerrors | v0.0.0-20200804184101-5ec99f83aff1 | — | — | — | — |
| google.golang.org/appengine | — | — | — | — | v1.4.0 |
Moved: 1 · unchanged at every release: 3
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: stage-unknown.
- No release in this window recorded a passing observation at UNKNOWN.
- Releases in this window never measured at UNKNOWN: 4
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.