Records/golang/cloud.google.com/go/failure issue

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.46.3 PASS 1 passing observations
• v0.45.1 not measured
• v0.44.2 not measured
• v0.44.1 not measured
• v0.38.0 FAIL
• v0.37.0 PASS 1 passing observations

Where it reproduced

• os=linux · runtime=go@1.26 ×1 2026-10-18 → 2026-10-18

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.37.0 → first failing release v0.38.0

  What differs across the boundary

  • github.com/golang/protobuf v1.2.0, v1.3.1, v1.5.4 → v1.3.1 hypothesis
  • github.com/google/go-cmp v0.2.0, v0.6.0 → v0.3.0 hypothesis
  • github.com/google/pprof v0.0.0-20181206194817-3ea8567a2e57, v0.0.0-20231212022811-ec68065c825e → v0.0.0-20181206194817-3ea8567a2e57 hypothesis
  • github.com/googleapis/gax-go/v2 v2.0.3 → v2.0.5 hypothesis
  • golang.org/x/build v0.0.0-20190111050920-041ab4dc3f9d → — hypothesis
  • golang.org/x/exp — → v0.0.0-20190121172915-509febef88a4 hypothesis
  • golang.org/x/lint v0.0.0-20190227174305-5b3e6a55c961 → v0.0.0-20190409202823-959b441ac422 hypothesis
  • golang.org/x/oauth2 v0.0.0-20181203162652-d668ce993890, v0.0.0-20190226205417-e64efc72b421, v0.16.0 → v0.0.0-20190604053449-0f29369cfe45 hypothesis
  • golang.org/x/sync v0.0.0-20190227155943-e225da77a7e6, v0.12.0 → v0.0.0-20190423024810-112230192c58 hypothesis
  • golang.org/x/text v0.23.0, v0.3.1-0.20180807135948-17ff2d5776d2 → v0.3.2 hypothesis
  • golang.org/x/time v0.0.0-20181108054448-85acf8d2951c, v0.11.0 → v0.0.0-20181108054448-85acf8d2951c hypothesis
  • golang.org/x/tools v0.0.0-20190226205152-f727befe758c, v0.31.0 → v0.0.0-20190506145303-2d16b83fe98c hypothesis
  • google.golang.org/api v0.1.0 → v0.13.0, v0.15.0, v0.8.0, v0.9.0 hypothesis
  • google.golang.org/genproto v0.0.0-20190306203927-b5d61aea6440 → v0.0.0-20190502173448-54afdca5d873 hypothesis
  • google.golang.org/grpc v1.19.0, v1.67.1 → v1.20.1 hypothesis
  • honnef.co/go/tools v0.0.0-20190106161140-3f1c8253044a → v0.0.0-20190418001031-e561f6794a2a 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 v0.38.0 → first passing release v0.46.3

  Releases between them never measured at this stage: 3

  What differs across the boundary

  • cloud.google.com/go/bigquery v1.0.1, v1.3.0 → — hypothesis
  • cloud.google.com/go/datastore v1.0.0 → — hypothesis
  • cloud.google.com/go/pubsub v1.0.1, v1.1.0 → — hypothesis
  • github.com/golang/mock v1.3.1 → v1.2.0 hypothesis
  • github.com/golang/protobuf v1.3.2 → v1.3.1 hypothesis
  • github.com/google/btree — → v0.0.0-20180813153112-4030bb1f1f0c hypothesis
  • github.com/google/pprof v0.0.0-20190515194954-54271f7e092f → v0.0.0-20181206194817-3ea8567a2e57 hypothesis
  • golang.org/x/exp v0.0.0-20190829153037-c13cbed26979, v0.0.0-20191030013958-a1ab85dbe136 → v0.0.0-20190121172915-509febef88a4 hypothesis
  • golang.org/x/lint v0.0.0-20190909230951-414d861bb4ac, v0.0.0-20190930215403-16217165b5de → v0.0.0-20190409202823-959b441ac422 hypothesis
  • golang.org/x/net v0.0.0-20190620200207-3b0461eec859 → — hypothesis
  • golang.org/x/sync — → v0.0.0-20190423024810-112230192c58 hypothesis
  • golang.org/x/time — → v0.0.0-20181108054448-85acf8d2951c hypothesis
  • golang.org/x/tools v0.0.0-20190911174233-4f2ddba30aff, v0.0.0-20191113191852-77e3bb0ad9e7, v0.0.0-20191115202509-3a792d9c32b2 → v0.0.0-20190506145303-2d16b83fe98c hypothesis
  • google.golang.org/api v0.13.0, v0.14.0, v0.9.0 → v0.13.0, v0.15.0, v0.8.0, v0.9.0 hypothesis
  • google.golang.org/genproto v0.0.0-20190911173649-1774047e7e51, v0.0.0-20191108220845-16a3f7862a1a, v0.0.0-20191115194625-c23dd37a84c9 → v0.0.0-20190502173448-54afdca5d873 hypothesis
  • google.golang.org/grpc v1.21.1 → v1.20.1 hypothesis
  • honnef.co/go/tools v0.0.1-2019.2.3 → v0.0.0-20190418001031-e561f6794a2a 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: 17 · unchanged at every release: 8

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_COMPILE: 3
• No failure domain was inferred for this failure.

Published answers for the affected releases

No published sample names these releases.