Recordsgolanggithub.com/kr/prettyfailure issue
Failure signature
PROJECT_TEST exit 1 ×1
--- FAIL: TestCCheck (0.00s) · === RUN TestCDeferAndDone · contract_test.go:<n>: expected 2 deferred functions to run on Done(), got 0 …
Evidence quality: complete · go/test · test-runner-diagnostic · outer go test · First recorded: 2026-09-06 · Last seen: 2026-09-06
sha256:f33789b8002b…
Where it was measured
PASS means the release recorded a passing observation at PROJECT_TEST 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-06 → 2026-09-06
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 | v0.3.1 | v0.2.1 | v0.2.0 | v0.1.0 |
|---|---|---|---|---|
| github.com/kr/text | v0.2.0 | v0.1.0 | v0.1.0 | v0.1.0 |
| github.com/rogpeppe/go-internal | v1.9.0 | — | — | — |
Moved: 1 · 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
- No release in this window recorded a passing observation at PROJECT_TEST.
- Releases in this window never measured at PROJECT_TEST: 3
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.