Recordsgolanggithub.com/stretchr/testifyfailure issue
Failure signature
PROJECT_RESOLVE exit 1 ×1
<path>:<n>:<n>: missing go.sum entry for module providing package github.com/stretchr/objx (imported by github.com/stretchr/testify/mock); to add:
Evidence quality: complete · go/module · resolve-diagnostic · outer go run · First recorded: 2026-09-03 · Last seen: 2026-09-03
sha256:0d0008e28623…
github.com/stretchr/testify/mock.AnythingOfType github.com/stretchr/testify/mock.Mock github.com/stretchr/testify/mock.TestingT
Where it was measured
PASS means the release recorded a passing observation at PROJECT_RESOLVE and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- v1.11.1 not measured
- v1.10.0 not measured
- v1.9.0 not measured
- v1.8.4 FAIL
- v1.8.1 not measured
- v1.8.0 not measured
- v1.7.1 not measured
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-09-03 → 2026-09-03
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.11.1 | v1.10.0 | v1.9.0 | v1.8.4 | v1.8.1 | v1.8.0 | v1.7.1 |
|---|---|---|---|---|---|---|---|
| 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 |
| 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 |
| github.com/stretchr/objx | v0.5.2 | — | v0.5.2 | v0.5.3 | v0.2.0 | v0.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.0-20210107192922-496545a6307b |
Moved: 4 · unchanged at every release: 0
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_RESOLVE.
- Releases in this window never measured at PROJECT_RESOLVE: 6
- No failure domain was inferred for this failure.
Published answers for the affected releases
- github.com/stretchr/testify v1.8.4: mock.Mock 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. HOWgithub.com/stretchr/testify/mock.Mock MIT-0 · 2026-09-03
- github.com/stretchr/testify v1.8.4: mock.Mock 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. HOWmock.Mock MIT-0 · 2026-09-03
- github.com/stretchr/testify v1.8.4: assert.Eventually, assert.Never 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. HOWassert.Eventuallyassert.Never MIT-0 · 2026-09-03