Recordsgolanggo.uber.org/atomicfailure issue
Failure signature
PROJECT_COMPILE exit 1 ×1
<path> <str> imported and not used
Evidence quality: complete · go/compiler · compiler-diagnostic · outer go run · First recorded: 2026-09-16 · Last seen: 2026-09-16
sha256:964ddac6b19a…
go.uber.org/atomic.Bool go.uber.org/atomic.Duration go.uber.org/atomic.Int64 go.uber.org/atomic.NewBool go.uber.org/atomic.NewDuration go.uber.org/atomic.NewFloat64 go.uber.org/atomic.NewInt64 go.uber.org/atomic.NewString go.uber.org/atomic.String
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.
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-09-16 → 2026-09-16
Nearest known PASS/FAIL boundaries
No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.
Dependency versions across releases
What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.
| Library | v1.6.0 | v1.5.0 |
|---|---|---|
| github.com/stretchr/testify | v1.3.0 | v1.4.0 |
| golang.org/x/lint | v0.0.0-20190930215403-16217165b5de | v0.0.0-20190930215403-16217165b5de |
Moved: 1 · unchanged at every release: 1
An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.
Evidence gaps
- No release in this window recorded a passing observation at PROJECT_COMPILE.
- Releases in this window never measured at PROJECT_COMPILE: 1
- No failure domain was inferred for this failure.
Published answers for the affected releases
- go.uber.org/atomic v1.6.0 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-09-15