Recordsgolanggolang.org/x/syncfailure issue
Failure signature
PROJECT_TEST exit 1 ×1
--- FAIL: TestRRInvalidStringHandling (0.00s) · === RUN TestRRInDNSMessage · --- PASS: TestRRInDNSMessage (0.00s) · FAIL example.com/dnsrr/test 0.006s
Evidence quality: complete · go/test · test-runner-diagnostic · outer go test · First recorded: 2026-09-04 · Last seen: 2026-09-04
sha256:9e6fd3f3d1dd…
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.17.0 PASS 7 passing observations
- v0.12.0 PASS 21 passing observations
- v0.8.0 PASS 1 passing observations
- v0.7.0 FAIL
- v0.0.0-20200625203802-6e8e738ad208 not measured
- v0.0.0-20200317015054-43a5402ce75a not measured
- v0.0.0-20181108010431-42b317875d0f not measured
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-09-04 → 2026-09-04
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 failing release v0.7.0 → first passing release v0.8.0
One side of this boundary has no resolved dependency tree, so nothing could be compared.
Evidence gaps
- Releases in this window never measured at PROJECT_TEST: 3
- No resolved dependency tree for v0.8.0 or for v0.7.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.