Records/golang/google.golang.org/grpc/failure issue

Where it was measured

PASS means the release recorded a passing observation at PROJECT_TEST and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.

• v1.83.0 PASS 6 passing observations
• v1.83.0-dev not measured
• v1.81.0 PASS 6 passing observations
• v1.80.0 FAIL
• v1.79.2 PASS 4 passing observations
• v1.75.1 PASS 2 passing observations
• v1.71.0 PASS 14 passing observations

Where it reproduced

• os=linux · runtime=go@1.26 ×1 2026-08-31 → 2026-08-31

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 v1.79.2 → first failing release v1.80.0

  One side of this boundary has no resolved dependency tree, so nothing could be compared.

• Last failing release v1.80.0 → first passing release v1.81.0

  What differs across the boundary

  • github.com/cncf/xds/go — → v0.0.0-20251210132809-ee656c7534f5 hypothesis
  • github.com/envoyproxy/go-control-plane — → v0.14.0 hypothesis
  • github.com/envoyproxy/go-control-plane/envoy — → v1.36.0 hypothesis
  • github.com/golang/glog — → v1.2.5 hypothesis
  • github.com/spiffe/go-spiffe/v2 — → v2.6.0 hypothesis
  • go.opentelemetry.io/contrib/detectors/gcp — → v1.39.0 hypothesis
  • golang.org/x/net v0.55.0 → v0.52.0 hypothesis
  • golang.org/x/oauth2 v0.36.0 → v0.35.0 hypothesis
  • golang.org/x/sys v0.45.0 → v0.42.0 hypothesis
  • gonum.org/v1/gonum — → v0.17.0 hypothesis
  • google.golang.org/genproto/googleapis/rpc v0.0.0-20260427160629-7cedc36a6bc4 → v0.0.0-20260401024825-9d38bb4040a9, v0.0.0-20260406210006-6f92a3bedf2d hypothesis

  A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.

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: 19 · unchanged at every release: 5

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

• Releases in this window never measured at PROJECT_TEST: 1
• No resolved dependency tree for v1.79.2 or for v1.80.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.