Recordsgolanggolang.org/x/toolsfailure issue
Failure signature
PROJECT_TEST exit 1 ×1
--- FAIL: TestTSIGMessageCreationAndVerification (0.00s) · === RUN TestTSIGVerificationFailsWithBadSecret …
Evidence quality: complete · go/test · test-runner-diagnostic · outer go test · First recorded: 2026-08-31 · Last seen: 2026-08-31
sha256:e0f31904e665…
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.47.0 not measured
- v0.44.0 PASS 16 passing observations
- v0.43.0 not measured
- v0.40.0 FAIL
- v0.36.0 not measured
- v0.31.0 PASS 29 passing observations
- v0.22.0 PASS 8 passing observations
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.31.0 → first failing 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.
-
Last failing release v0.40.0 → first passing release v0.44.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.
| Library | v0.47.0 | v0.44.0 | v0.31.0 | v0.22.0 |
|---|---|---|---|---|
| github.com/google/go-cmp | — | v0.7.0 | v0.6.0 | v0.6.0 |
| github.com/yuin/goldmark | — | v1.8.2 | — | v1.4.13 |
| golang.org/x/mod | v0.37.0 | v0.35.0 | — | v0.18.0 |
| golang.org/x/net | — | v0.55.0 | v0.38.0 | v0.31.0 |
| golang.org/x/sync | v0.21.0 | v0.20.0 | v0.12.0 | v0.7.0 |
| golang.org/x/telemetry | — | v0.0.0-20260409153401-be6f6cb8b1fa | — | v0.0.0-20240521205824-bda55230c457 |
Moved: 6 · unchanged at every release: 0
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.31.0 or for v0.40.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
No published sample names these releases.