Recordsgolanggithub.com/stretchr/testifyfailure issue
Failure signature
UNKNOWN exit 1 Evidence gap ×1
go: downloading github.com/opentracing/opentracing-go v1.1.0 · panic: runtime error: comparing uncomparable type mocktracer.MockSpanContext …
Evidence quality: complete · go · unclassified-diagnostic · outer go run · gap stage-unknown · First recorded: 2026-10-24 · Last seen: 2026-10-24
sha256:617ea66c61e4…
Where it was measured
PASS means the release recorded a passing observation at UNKNOWN and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-10-24 → 2026-10-24
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.12.1 | v1.11.1 | v1.10.0 | v1.9.0 |
|---|---|---|---|---|
| github.com/davecgh/go-spew | — | v1.1.2-0.20180830191138-d8f796af33cc | v1.1.1 | v1.1.1 |
| github.com/pmezard/go-difflib | — | v1.0.1-0.20181226105442-5d4384ee4fb2 | v1.0.0 | v1.0.0 |
| github.com/stretchr/objx | v0.5.3 | v0.5.2 | — | v0.5.2 |
| go.yaml.in/yaml/v3 | v3.0.5 | — | — | — |
| gopkg.in/yaml.v3 | — | v3.0.1 | v3.0.1 | v3.0.1 |
Moved: 3 · unchanged at every release: 2
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
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- The captured output could not establish: stage-unknown.
- No release in this window recorded a passing observation at UNKNOWN.
- Releases in this window never measured at UNKNOWN: 3
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.