Recordsgolanggolang.org/x/syncfailure issue
Failure signature
PROJECT_COMPILE exit 1 ×1
test/contract.go:<n>:<n>: <str> imported and not used
Evidence quality: complete · go/compiler · compiler-diagnostic · outer go run · First recorded: 2026-10-24 · Last seen: 2026-10-24
sha256:d5fae02e8604…
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.12.0 PASS 2 passing observations
- v0.8.0 PASS 2 passing observations
- v0.7.0 not measured
- v0.0.0-20201207232520-09787c993a3a FAIL
- v0.0.0-20200625203802-6e8e738ad208 PASS 2 passing observations
- v0.0.0-20200317015054-43a5402ce75a PASS 2 passing observations
- v0.0.0-20190911185100-cd5d95a43a6e not measured
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-10-24 → 2026-10-24
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.0.0-20200625203802-6e8e738ad208 → first failing release v0.0.0-20201207232520-09787c993a3a
One side of this boundary has no resolved dependency tree, so nothing could be compared.
-
Last failing release v0.0.0-20201207232520-09787c993a3a → first passing release v0.8.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.
Evidence gaps
- Releases in this window never measured at PROJECT_COMPILE: 2
- No resolved dependency tree for v0.0.0-20200625203802-6e8e738ad208 or for v0.0.0-20201207232520-09787c993a3a, 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.