Records golang go.uber.org/atomicv1.6.0

Which symbol ran where

Symbols × operating systems for this version. Cells drill into the package's compatibility cube.

○ 62026-09-16

	debian glibc	ubuntu glibc
go.uber.org/atomic.Bool		80%5
go.uber.org/atomic.Duration		80%5
go.uber.org/atomic.Int64		80%5
go.uber.org/atomic.NewBool		80%5
go.uber.org/atomic.NewDuration		80%5
go.uber.org/atomic.NewFloat64		80%5

Showing the environments with the most evidence.

Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.

no sample at this coordinate yet
there is a sample here, and nothing of ours has run it at this coordinate yet
there is a sample here, and our run of it at this coordinate came back clean
there is a sample here, and our run of it at this coordinate failed
there is a sample here, and this coordinate records both a passing and a failing run of it
nothing recorded — unknown, never "works" and never "broken"
there is a level below this cell — click to open it

A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.

Environment detail

Project-level observations and symbol/contract verifications are counted separately and never combined.

These counts do not distinguish how the symbol was called: overloads, argument shapes and options are pooled together. What a particular call shape does is proven by a sample's contract, not by these numbers.

Environment	Confidence	Observations	Verified	Pass rate	Peers	Last seen
go 1.26 · Go · go · linux glibc · docker Usage: USED 2✓	LOW	0 +2	0	—	1	2026-09-07
go 1.26 · Go · go · linux glibc · docker Observations: PROJECT_LOAD 2✓ · PROJECT_TEST 2✓ — Usage: USED 5✓ — Verified: CONTRACT 1✓	LOW	4 +5	1	100%	1 · 1✓	2026-09-17
go 1.26 · Go · go · linux glibc Observations: PROJECT_COMPILE 0✓ 1✕ · PROJECT_PROCESS 4✓ · PROJECT_TEST 1✓ — Usage: USED 6✓	LOW	6 +6	0	83%	1	2026-09-16
go 1.26 · Go · go · linux glibc · docker Usage: USED 1✓	LOW	0 +1	0	—	1	2026-09-07
go 1.26 · Go · go · linux glibc · docker Usage: USED 1✓	LOW	0 +1	0	—	1	2026-09-16

Recent failure clusters

observed PROJECT_COMPILE exit 1 ×1 v1.6.0 os=linux · runtime=go@1.26 go.uber.org/atomic.Bool sha256:964ddac6b19a…
<path> <str> imported and not used
go/compiler · compiler-diagnostic · outer go run

Evidence quality: complete · Environment variants: 1 · First recorded: 2026-09-16 · Last seen: 2026-09-16

Where does this failure start and stop?

Symbols

Published samples

go.uber.org/atomic v1.6.0 HOW MIT-0 · 2026-09-15