Recordsgolanggo.yaml.in/yaml/v2failure issue
Failure signature
PROJECT_COMPILE exit 1 ×1
<path> undefined: model.ParseMetric
Evidence quality: complete · go/compiler · compiler-diagnostic · outer go run · First recorded: 2026-09-02 · Last seen: 2026-09-02
sha256:46671bb8c671…
Where it was measured
PASS means the release recorded a passing observation at PROJECT_COMPILE 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-09-02 → 2026-09-02
Nearest known PASS/FAIL boundaries
The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.
-
Last failing release v2.4.3 → first passing release v2.4.4
One side of this boundary has no resolved dependency tree, so nothing could be compared.
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 | v2.4.4 | v2.4.2 |
|---|---|---|
| gopkg.in/check.v1 | — | v0.0.0-20161208181325-20d25e280405 |
Moved: 0 · 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.
Evidence gaps
- Releases in this window never measured at PROJECT_COMPILE: 1
- No resolved dependency tree for v2.4.4 or for v2.4.3, so the versions either side of the boundary could not be compared.
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.