Recordsgolanggoogle.golang.org/grpcfailure issue
Failure signature
PROJECT_TEST exit 1 ×1
--- FAIL: TestWithTimeoutContract (5.01s) · FAIL example.com/otlpmetrichttp-timeout/test 5.079s
Evidence quality: complete · go/test · test-runner-diagnostic · outer go test · First recorded: 2026-09-03 · Last seen: 2026-09-03
sha256:701b826e4bfb…
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.2 PASS 3 passing observations
- v1.83.1 FAIL
- v1.83.0 PASS 6 passing observations
- v1.83.0-dev not measured
- v1.81.0 PASS 6 passing observations
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-09-03 → 2026-09-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 passing release v1.83.0 → first failing release v1.83.1
What differs across the boundary
- go.opentelemetry.io/otel v1.44.0 → v1.46.0 hypothesis
- go.opentelemetry.io/otel/metric v1.44.0 → v1.46.0 hypothesis
- go.opentelemetry.io/otel/sdk v1.44.0 → v1.46.0 hypothesis
- go.opentelemetry.io/otel/sdk/metric v1.44.0 → v1.46.0 hypothesis
- go.opentelemetry.io/otel/trace v1.44.0 → v1.46.0 hypothesis
- golang.org/x/net v0.55.0 → v0.58.0 hypothesis
- golang.org/x/sync v0.20.0 → v0.22.0 hypothesis
- golang.org/x/sys v0.45.0 → v0.47.0 hypothesis
- google.golang.org/genproto/googleapis/rpc v0.0.0-20260526163538-3dc84a4a5aaa → v0.0.0-20260819154853-08b0e4226688 hypothesis
- google.golang.org/protobuf v1.36.11 → v1.36.12 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.
-
Last failing release v1.83.1 → first passing release v1.83.2
What differs across the boundary
- google.golang.org/genproto/googleapis/rpc v0.0.0-20260825221802-da73d73af1c5 → v0.0.0-20260819154853-08b0e4226688 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: 10 · unchanged at every release: 14
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 failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.