Recordsgolanggolang.org/x/syncfailure issue
Failure signature
UNKNOWN exit 1 Evidence gap ×1
golang.org/x/sys/unix: <path>: chdir <path>: no such file or directory · # golang.org/x/text/transform · open <path>: no such file or directory …
Evidence quality: complete · go · unclassified-diagnostic · outer go run · gap stage-unknown · First recorded: 2026-10-25 · Last seen: 2026-10-25
sha256:a8f9bf952b0a…
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.12.0 not measured
- v0.8.0 not measured
- v0.7.0 not measured
- v0.0.0-20201207232520-09787c993a3a FAIL
- v0.0.0-20200625203802-6e8e738ad208 not measured
- v0.0.0-20200317015054-43a5402ce75a not measured
- v0.0.0-20190911185100-cd5d95a43a6e not measured
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-10-25 → 2026-10-25
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.
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.