Recordsgolanggolang.org/x/expfailure issue
Failure signature
UNKNOWN exit 1 Evidence gap ×1
go: build output <str> already exists and is a directory
Evidence quality: complete · go · unclassified-diagnostic · outer go build · gap stage-unknown · First recorded: 2026-10-18 · Last seen: 2026-10-18
sha256:0882784d80c2…
Where it was measured
PASS means the release recorded a passing observation at UNKNOWN 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-20200331195152-e8c3332aa8e5 not measured
- v0.0.0-20200224162631-6cc2880d07d6 not measured
- v0.0.0-20200207192155-f17229e696bd FAIL
- v0.0.0-20200119233911-0405dc783f0a not measured
- v0.0.0-20191227195350-da58074b4299 not measured
- v0.0.0-20191030013958-a1ab85dbe136 not measured
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-10-18 → 2026-10-18
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: 5 · unchanged at every release: 7
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
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- The captured output could not establish: stage-unknown.
- No release in this window recorded a passing observation at UNKNOWN.
- Releases in this window never measured at UNKNOWN: 6
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.