Recordsgolanggithub.com/envoyproxy/go-control-planefailure issue
Failure signature
UNKNOWN exit 1 Evidence gap ×3
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-23 · Last seen: 2026-10-23
sha256:0882784d80c2…
github.com/envoyproxy/go-control-plane/envoy/config/endpoint/v3.ClusterLoadAssignment github.com/envoyproxy/go-control-plane/pkg/cache/types.Resource github.com/envoyproxy/go-control-plane/pkg/cache/v3.NewLinearCache github.com/envoyproxy/go-control-plane/pkg/cache/v3.Request github.com/envoyproxy/go-control-plane/pkg/cache/v3.WithInitialResources github.com/envoyproxy/go-control-plane/pkg/cache/v3.WithVersionPrefix github.com/envoyproxy/go-control-plane/pkg/log.Logger github.com/envoyproxy/go-control-plane/pkg/log.LoggerFuncs github.com/envoyproxy/go-control-plane/pkg/resource/v3.EndpointType github.com/envoyproxy/go-control-plane/pkg/wellknown.HTTPConnectionManager github.com/envoyproxy/go-control-plane/pkg/wellknown.Router
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.14.0 not measured
- v0.9.9-0.20210512163311-63b5d3c536b0 FAIL
- v0.9.9-0.20210217033140-668b12f5399d not measured
- v0.9.9-0.20201210154907-fd9021fe5dad not measured
- v0.9.4 not measured
Where it reproduced
- os=linux · runtime=go@1.26 ×3 2026-10-23 → 2026-10-23
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: 10 · unchanged at every release: 6
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: 4
- No failure domain was inferred for this failure.
Published answers for the affected releases
- github.com/envoyproxy/go-control-plane v0.9.9-0.20210512163311-63b5d3c536b0: types.Resource This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWgithub.com/envoyproxy/go-control-plane/pkg/cache/types.Resource MIT-0 · 2026-10-23
- github.com/envoyproxy/go-control-plane v0.9.9-0.20210512163311-63b5d3c536b0: v3.ClusterLoadAssignment This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWgithub.com/envoyproxy/go-control-plane/envoy/config/endpoint/v3.ClusterLoadAssignment MIT-0 · 2026-10-23
- github.com/envoyproxy/go-control-plane v0.9.9-0.20210512163311-63b5d3c536b0: log.LoggerFuncs This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWlog.LoggerFuncs MIT-0 · 2026-10-23