Recordsgolanggolang.org/x/syncfailure issue
Failure signature
PROJECT_COMPILE exit 1 ×1
<path> cannot use fudge (variable of type int64) as uint16 value in argument to m.SetTsig …
Evidence quality: complete · go/compiler · compiler-diagnostic · outer go test · First recorded: 2026-08-31 · Last seen: 2026-08-31
sha256:ba833ce87b90…
Where it was measured
PASS means the release recorded a passing observation at PROJECT_COMPILE and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- v0.22.0 PASS 2 passing observations
- v0.21.0 not measured
- v0.20.0 not measured
- v0.19.0 FAIL
- v0.17.0 not measured
- v0.12.0 PASS 2 passing observations
- v0.8.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.12.0 → first failing release v0.19.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.19.0 → first passing release v0.22.0
Releases between them never measured at this stage: 2
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_COMPILE: 4
- No resolved dependency tree for v0.12.0 or for v0.19.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.