Recordsgolanggithub.com/go-stack/stackfailure issue
Failure signature
PROJECT_TEST exit 1 ×1
--- FAIL: TestContractCaller (0.00s) · === RUN TestContractTrace · contract_test.go:<n>: expected non-empty trimmed stack …
Evidence quality: complete · go/test · test-runner-diagnostic · outer go test · First recorded: 2026-08-31 · Last seen: 2026-08-31
sha256:a118e7823282…
github.com/go-stack/stack.Call github.com/go-stack/stack.CallStack github.com/go-stack/stack.Caller github.com/go-stack/stack.Trace
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-08-31 → 2026-08-31
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 v1.6.0 → first passing release v1.8.0
Both trees resolved every dependency to the same version. Nothing here moved.
Evidence gaps
- Releases in this window never measured at PROJECT_TEST: 1
- No failure domain was inferred for this failure.
Published answers for the affected releases
- github.com/go-stack/stack v1.6.0: capture and format call stack and caller frames with stack.Caller and stack.Trace 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. HOWstack.Callerstack.Tracego 1.26.6 MIT-0 · 2026-08-28