Recordsgolanggolang.org/x/sysfailure issue
Failure signature
PROJECT_COMPILE exit 1 ×3
<path> undefined: gax.WithPathTemplateHeader
Evidence quality: complete · go/compiler · compiler-diagnostic · outer go run · First recorded: 2026-10-14 · Last seen: 2026-10-14
sha256:c9bba5a5b078…
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.47.0 PASS 487 passing observations
- v0.45.0 not measured
- v0.44.0 not measured
- v0.43.0 not measured
- v0.42.0 FAIL
- v0.41.0 PASS 3 passing observations
- v0.40.0 PASS 4 passing observations
- v0.39.0 PASS 5 passing observations
Where it reproduced
- os=linux · runtime=go@1.26 ×3 2026-10-14 → 2026-10-14
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.41.0 → first failing release v0.42.0
One side of this boundary has no resolved dependency tree, so nothing could be compared.
-
Last failing release v0.42.0 → first passing release v0.47.0
Releases between them never measured at this stage: 4
One side of this boundary has no resolved dependency tree, so nothing could be compared.
Evidence gaps
- Releases in this window never measured at PROJECT_COMPILE: 3
- No resolved dependency tree for v0.41.0 or for v0.42.0, 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.