CodeSampleX

Recordsgolanggithub.com/stretchr/testifyv1.11.1assert.ElementsMatch

Change the conditions
Fixed
OSlinux Symbolassert.ElementsMatch
Filter Runtimego 1.26 Package versionv1.11.1 Architecturex64 Package managergomod Execution contextgo libcmusl Clear filters

Current conditions

assert.ElementsMatch @v1.11.1linux · musl · x64 · go 1.26 · gomod · go

1 of 1 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate came back clean (1)

Project observations
nothing at this coordinate
Contract verifications
1 / 1
Last recorded
2026-08-18

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 7 · Steady 0

First observed break

v1.11.1

windows · go@1.26

3 FAIL · stage: PROJECT_TEST

Library Version Health Measured there Projects
github.com/davecgh/go-spew v1.1.1 CANDIDATE Correlated change; unproven combination contract passed 122 project-days
github.com/davecgh/go-spew v1.1.2-0.20180830191138-d8f796af33cc CANDIDATE Correlated change; unproven combination nothing measured 7 project-days
github.com/pmezard/go-difflib v1.0.0 CANDIDATE Correlated change; unproven combination contract passed 122 project-days
github.com/pmezard/go-difflib v1.0.1-0.20181226105442-5d4384ee4fb2 CANDIDATE Correlated change; unproven combination nothing measured 7 project-days
github.com/stretchr/objx v0.1.0 CANDIDATE Correlated change; unproven combination contract passed 5 project-days
github.com/stretchr/objx v0.5.2 CANDIDATE Correlated change; unproven combination builds observed 5 project-days
gopkg.in/yaml.v3 v3.0.1 CANDIDATE Correlated change; unproven combination contract passed 129 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.

Moved: 5 · 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.