CodeSampleX

Recordsgolanggo.uber.org/atomicv1.6.0go.uber.org/atomic.Duration

Change the conditions
Fixed
OSubuntu glibc Symbolgo.uber.org/atomic.Duration libcglibc
Filter Runtimego 1.26 Package versionv1.6.0 Architecturex64 Package managergo 1 Clear filters

Current conditions

go.uber.org/atomic.Duration @v1.6.0ubuntu glibc · x64 · go 1.26 · go 1

4 of 5 passed

Observed — real project builds reported from this coordinate.

no sample at this coordinate yet

Project observations
4 / 5
Contract verifications
nothing at this coordinate
Independent reporting peers
1
Last recorded
2026-09-16
Evidence you can open

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 3 · Steady 1

First observed break

v1.6.0

linux · go@1.26

1 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:964ddac6b19a356d0ae3f5727559d1fc36ac1222ed1964d18326e8a89565fde3

View exact conditions View failure cluster
Library Version Health Measured there Projects
github.com/stretchr/testify v1.3.0 CANDIDATE Correlated change; unproven combination contract passed 2 project-days
github.com/stretchr/testify v1.7.0 CANDIDATE Correlated change; unproven combination contract passed 6 project-days
github.com/stretchr/testify v1.8.1 CANDIDATE Correlated change; unproven combination contract passed 10 project-days
golang.org/x/lint v0.0.0-20190930215403-16217165b5de PASS All observations passed contract passed 18 project-days

The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.

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.

Libraryv1.6.0v1.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.

Recent failure clusters