Recordsgolanggolang.org/x/syncfailure issue
Failure signature
PROJECT_TEST exit 1 ×1
FAIL explore [setup failed]
Evidence quality: complete · go/test · test-runner-diagnostic · outer go test · First recorded: 2026-09-02 · Last seen: 2026-09-02
sha256:65e540a1f555…
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.23.0 not measured
- v0.22.0 FAIL
- v0.21.0 PASS 6 passing observations
- v0.20.0 PASS 17 passing observations
- v0.19.0 PASS 1 passing observations
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-09-02 → 2026-09-02
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.21.0 → first failing release v0.22.0
Both trees resolved every dependency to the same version. Nothing here moved.
Evidence gaps
- Releases in this window never measured at PROJECT_TEST: 1
- No failure domain was inferred for this failure.
Published answers for the affected releases
- golang.org/x/sync v0.22.0: syncmap.Map This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWgolang.org/x/sync/syncmap.Map MIT-0 · 2026-08-27
- golang.org/x/sync v0.22.0: errgroup.WithContext, errgroup.Group.SetLimit, semaphore.NewWeighted This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWerrgroup.WithContexterrgroup.Group.SetLimitsemaphore.NewWeightedsingleflight.Group MIT-0 · 2026-08-20