Recordsgolanggolang.org/x/expfailure issue
Failure signature
PROJECT_COMPILE exit 1 ×1
<path> <str> imported and not used
Evidence quality: complete · go/compiler · compiler-diagnostic · outer go run · First recorded: 2026-09-20 · Last seen: 2026-09-20
sha256:964ddac6b19a…
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.
- v0.0.0-20230515195305-f3d0a9c9a5cc not measured
- v0.0.0-20200224162631-6cc2880d07d6 not measured
- v0.0.0-20190121172915-509febef88a4 not measured
- v0.0.0-20181106170214-d68db9428509 FAIL
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-09-20 → 2026-09-20
Nearest known PASS/FAIL boundaries
No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.
Dependency versions across releases
What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.
Moved: 2 · unchanged at every release: 8
An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.
Evidence gaps
- No release in this window recorded a passing observation at PROJECT_COMPILE.
- Releases in this window never measured at PROJECT_COMPILE: 3
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.