Recordsgolanggolang.org/x/xerrorsfailure issue
Failure signature
PROJECT_COMPILE exit 1 ×1
<path>:<n>:<n>: undefined: errors.Frame · <path>:<n>:<n>: undefined: errors.Caller · <path>:<n>:<n>: undefined: errors.Formatter …
Evidence quality: complete · go/compiler · compiler-diagnostic · outer go run · First recorded: 2026-11-03 · Last seen: 2026-11-03
sha256:b6a788006c9f…
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-20191204190536-9bdfabe68543 PASS 8 passing observations
- v0.0.0-20191011141410-1b5146add898 PASS 4 passing observations
- v0.0.0-20190717185122-a985d3407aa7 PASS 1 passing observations
- v0.0.0-20190513163551-3ee3066db522 FAIL
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-11-03 → 2026-11-03
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 v0.0.0-20190513163551-3ee3066db522 → first passing release v0.0.0-20190717185122-a985d3407aa7
One side of this boundary has no resolved dependency tree, so nothing could be compared.
Evidence gaps
- No resolved dependency tree for v0.0.0-20190717185122-a985d3407aa7 or for v0.0.0-20190513163551-3ee3066db522, 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.