Recordsgolanggithub.com/felixge/httpsnoopfailure issue
Failure signature
PROJECT_COMPILE exit 1 ×1
test/contract_test.go:<n>:<n>: <str> imported and not used
Evidence quality: complete · go/compiler · compiler-diagnostic · outer go test · First recorded: 2026-09-01 · Last seen: 2026-09-01
sha256:02fe86edb6eb…
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-01 → 2026-09-01
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.0.4 → first passing 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.1.0 or for v1.0.4, 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.