Recordsgolanggithub.com/stretchr/testifyv1.7.0github.com/stretchr/testify/require
Change the conditions
Current conditions
github.com/stretchr/testify/require @v1.7.0debian glibc · x64 · go 1.26 · go · 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 (2)
- Project observations
- 1 / 1
- Contract verifications
- 1 / 1
- Independent reporting peers
- 1
- Last recorded
- 2026-09-17
Evidence you can open
Dependency Health
Observed combinations and failure evidence for this release
Observed problems 1 ·
Changed 7 ·
Steady 0
First observed break
v1.7.0
linux · go@1.26
1 FAIL
· stage: PROJECT_COMPILE
· fingerprint: sha256:4616263d81c5784b03ea302022226c1464dbb4683a56652b0dcf890c4be6ab45
| Library | Version | Health | Measured there | Projects |
|---|---|---|---|---|
| github.com/davecgh/go-spew | v1.1.0 | CANDIDATE Correlated change; unproven combination | contract passed | 13 project-days |
| github.com/davecgh/go-spew | v1.1.1 | CANDIDATE Correlated change; unproven combination | contract passed | 22 project-days |
| github.com/pmezard/go-difflib | v1.0.0 | CANDIDATE Correlated change; unproven combination | contract passed | 35 project-days |
| github.com/stretchr/objx | v0.1.0 | CANDIDATE Correlated change; unproven combination | contract passed | 19 project-days |
| github.com/stretchr/objx | v0.2.0 | CANDIDATE Correlated change; unproven combination | contract passed | 9 project-days |
| gopkg.in/yaml.v3 | v3.0.0-20200313102051-9f266ea9e77c | CANDIDATE Correlated change; unproven combination | contract passed | 28 project-days |
| gopkg.in/yaml.v3 | v3.0.1 | CANDIDATE Correlated change; unproven combination | contract passed | 5 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.
| Library | v1.12.1 | v1.11.1 | v1.10.0 | v1.9.0 | v1.8.4 | v1.8.1 | v1.8.0 | v1.7.5 | v1.7.1 | v1.7.0 | v1.6.1 | v1.5.1 | v1.4.0 | v1.3.0 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| github.com/davecgh/go-spew | — | v1.1.2-0.20180830191138-d8f796af33cc | v1.1.1 | v1.1.1 | v1.1.1 | v1.1.1 | v1.1.1 | v1.1.1 | v1.1.1 | v1.1.0 | v1.1.1 | v1.1.1 | v1.1.0 | v1.1.0 |
| github.com/pmezard/go-difflib | — | v1.0.1-0.20181226105442-5d4384ee4fb2 | v1.0.0 | v1.0.0 | v1.0.0 | v1.0.0 | v1.0.0 | v1.0.0 | v1.0.0 | v1.0.0 | v1.0.0 | v1.0.0 | v1.0.0 | v1.0.0 |
| github.com/stretchr/objx | v0.5.3 | v0.5.2 | — | v0.5.2 | v0.5.3 | v0.2.0 | v0.4.0 | — | — | v0.2.0 | v0.1.0 | v0.1.0 | v0.1.0 | v0.2.0 |
| gopkg.in/yaml.v2 | — | — | — | — | — | — | — | — | — | — | — | v2.3.0 | v2.4.0 | — |
| gopkg.in/yaml.v3 | — | v3.0.1 | v3.0.1 | v3.0.1 | v3.0.1 | v3.0.1 | v3.0.1 | v3.0.1 | v3.0.0-20210107192922-496545a6307b | v3.0.1 | v3.0.0-20200313102051-9f266ea9e77c | — | — | — |
| go.yaml.in/yaml/v3 | v3.0.5 | — | — | — | — | — | — | — | — | — | — | — | — | — |
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.
Recent failure clusters
-
observed PROJECT_COMPILE exit 1 ×1 v1.7.0 os=linux · runtime=go@1.26 sha256:4616263d81c5…test/contract.go:<n>:<n>: not enough arguments in call to require.Containsgo/compiler · compiler-diagnostic · outer go runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-06 · Last seen: 2026-09-06
-
observed UNKNOWN exit 1 Evidence gap ×1 v1.7.0 os=linux · runtime=go@1.26 sha256:2b72f6b1973f…assertion 2 failed: require.Equal should invoke Errorf and FailNow on mismatched strings · exit status 1go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-06 · Last seen: 2026-09-06Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 v1.7.0 os=linux · runtime=go@1.26 sha256:ddadabd848f4…assertion 3 failed: InEpsilon should succeed for actual near zero within epsilon · exit status 1go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-06 · Last seen: 2026-09-06Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 v1.7.0 os=linux · runtime=go@1.26 sha256:37c752ff44d1…testing: warning: no tests to run · assertion 1 failed: suite.Run did not execute expected Test methods or invoked non-Test method · exit status 1go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-06 · Last seen: 2026-09-06Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 v1.7.0 os=linux · runtime=go@1.26 sha256:df2c1a527fb4…panic: runtime error: invalid memory address or nil pointer dereference · [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x537401] …go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-06 · Last seen: 2026-09-06Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 v1.7.0 os=linux · runtime=go@1.26 sha256:e9407b4efb93…panic: runtime error: invalid memory address or nil pointer dereference · [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x537401] …go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-06 · Last seen: 2026-09-06Diagnostic re-verification candidate