Recordsgolanggithub.com/davecgh/go-spewfailure issue
Failure signature
PROJECT_COMPILE exit 1 ×1
test/contract.go:<n>:<n>: not enough arguments in call to require.Contains
Evidence quality: complete · go/compiler · compiler-diagnostic · outer go run · First recorded: 2026-09-06 · Last seen: 2026-09-06
sha256:4616263d81c5…
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-06 → 2026-09-06
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.1.0 → first passing release v1.1.1
One side of this boundary has no resolved dependency tree, so nothing could be compared.
Evidence gaps
- No resolved dependency tree for v1.1.1 or for v1.1.0, 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.