Records/golang/golang.org/x/sync/failure issue

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.22.0 PASS 25 passing observations
• v0.21.0 PASS 2 passing observations
• v0.20.0 FAIL
• v0.19.0 PASS 1 passing observations
• v0.17.0 PASS 7 passing observations
• v0.12.0 PASS 21 passing observations

Where it reproduced

• os=linux · runtime=go@1.26 ×1 2026-08-29 → 2026-08-29

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.19.0 → first failing release v0.20.0

  One side of this boundary has no resolved dependency tree, so nothing could be compared.

• Last failing release v0.20.0 → first passing release v0.21.0

  Both trees resolved every dependency to the same version. Nothing here moved.

Evidence gaps

• No resolved dependency tree for v0.19.0 or for v0.20.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

• golang.org/x/sync v0.20.0: errgroup.Group, errgroup.WithContext, singleflight.Group Built ? 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.Grouperrgroup.WithContextsingleflight.Groupsemaphore.Weightedgo 1.26 MIT-0 · 2026-08-20
• golang.org/x/sync v0.20.0 Built ? 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. HOW MIT-0 · 2026-08-19