Recordsgolanggithub.com/felixge/httpsnoopfailure issue
Failure signature
PROJECT_TEST exit 1 ×1
--- FAIL: TestHandlerContract (0.00s) · --- PASS: TestHandlerContract/PreservesResponse (0.00s) · --- FAIL: TestHandlerContract/CreatesTraceSpan (0.00s) …
Evidence quality: complete · go/test · test-runner-diagnostic · outer go test · First recorded: 2026-09-08 · Last seen: 2026-09-08
sha256:1d1713b4e7f8…
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-08 → 2026-09-08
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 passing release v1.0.4 → first failing release v1.1.0
One side of this boundary has no resolved dependency tree, so nothing could be compared.
Evidence gaps
- No resolved dependency tree for v1.0.4 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.