Recordsgolanggithub.com/modern-go/reflect2failure issue
Failure signature
PROJECT_TEST Evidence gap ×1
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-08-17 · Last seen: 2026-08-17
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.
- v1.0.2 FAIL
- v0.0.0-20180701023420-4b7aa43c6742 PASS 1 passing observations
Where it reproduced
- os=windows · runtime=go@1.26 ×1 2026-08-17 → 2026-08-17
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 v0.0.0-20180701023420-4b7aa43c6742 → first failing release v1.0.2
One side of this boundary has no resolved dependency tree, so nothing could be compared.
Evidence gaps
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- No resolved dependency tree for v0.0.0-20180701023420-4b7aa43c6742 or for v1.0.2, 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.