alloydbconn/internal/alloydb: TestRefreshDuration failed

[flaky-bot[bot]]

This test failed!

To configure my behavior, see the Flaky Bot documentation.

If I'm commenting on this issue too often, add the flakybot: quiet label and I will stop commenting.

---

commit: 9f9cd9593f7cd127b195c2c746fd033062972a1c buildURL: https://github.com/GoogleCloudPlatform/alloydb-go-connector/actions/runs/7770988406 status: failed

[flaky-bot[bot]]

Looks like this issue is flaky. :worried:

I'm going to leave this open and stop commenting.

A human should fix and close this.

---

When run at the same commit (9f9cd9593f7cd127b195c2c746fd033062972a1c), this test passed in one build (https://github.com/GoogleCloudPlatform/alloydb-go-connector/actions/runs/7770988406) and failed in another build (https://github.com/GoogleCloudPlatform/alloydb-go-connector/actions/runs/7770988406).

[enocom]

=== RUN   TestRefreshDuration/when_expiration_is_greater_than_1_hour
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xc0000005 code=0x0 addr=0x0 pc=0x14092a78a]

goroutine 39 [running]:
golang.org/x/oauth2.(*Token).Type(0x0)
	C:/Users/runneradmin/go/pkg/mod/golang.org/x/[email protected]/token.go:64 +0x2a
golang.org/x/oauth2.(*Token).SetAuthHeader(0x0, 0xc0000e0d00)
	C:/Users/runneradmin/go/pkg/mod/golang.org/x/[email protected]/token.go:85 +0x39
golang.org/x/oauth2.(*Transport).RoundTrip(0xc0001d0700, 0xc0000e0a00)
	C:/Users/runneradmin/go/pkg/mod/golang.org/x/[email protected]/transport.go:51 +0x5c9
net/http.send(0xc0000e0a00, {0x140ea6680, 0xc0001d0700}, {0x0?, 0xc000282040?, 0x0?})
	C:/hostedtoolcache/windows/go/1.21.6/x64/src/net/http/client.go:260 +0x9c7
net/http.(*Client).send(0xc0002819e0, 0xc0000e0a00, {0x0?, 0x140e9fe00?, 0x0?})
	C:/hostedtoolcache/windows/go/1.21.6/x64/src/net/http/client.go:181 +0x14f
net/http.(*Client).do(0xc0002819e0, 0xc0000e0a00)
	C:/hostedtoolcache/windows/go/1.21.6/x64/src/net/http/client.go:724 +0x11a9
net/http.(*Client).Do(...)
	C:/hostedtoolcache/windows/go/1.21.6/x64/src/net/http/client.go:590
cloud.google.com/go/alloydb/apiv1alpha.(*alloyDBAdminRESTClient).GetConnectionInfo.func1({0x140eae208?, 0xc0002f8310}, {0x140d9d4f8, {0x0, 0x0, 0x0}, {0x0, 0x0}, 0xdf8475800})
	C:/Users/runneradmin/go/pkg/mod/cloud.google.com/go/[email protected]/apiv1alpha/alloydb_admin_client.go:4027 +0x30b
github.com/googleapis/gax-go/v2.invoke({0x140eae[160](https://github.com/GoogleCloudPlatform/alloydb-go-connector/actions/runs/7770988406/job/21191770635#step:6:161), 0xc0004680f0}, 0xc00036db18, {0x140d9d4f8, {0x0, 0x0, 0x0}, {0x0, 0x0}, 0xdf8475800}, ...)
	C:/Users/runneradmin/go/pkg/mod/github.com/googleapis/gax-go/[email protected]/invoke.go:82 +0x1d5
github.com/googleapis/gax-go/v2.Invoke({0x140eae160, 0xc0004680f0}, 0xc0004a8080?, {0xc0001d0820, 0x2, 0x80?})
	C:/Users/runneradmin/go/pkg/mod/github.com/googleapis/gax-go/[email protected]/invoke.go:50 +0x1b0
cloud.google.com/go/alloydb/apiv1alpha.(*alloyDBAdminRESTClient).GetConnectionInfo(0xc0002b4380, {0x140eae160, 0xc0004680f0}, 0xc000386640, {0x0, 0x0, 0x1000000001d08?})
	C:/Users/runneradmin/go/pkg/mod/cloud.google.com/go/[email protected]/apiv1alpha/alloydb_admin_client.go:4016 +0xcf3
cloud.google.com/go/alloydb/apiv1alpha.(*AlloyDBAdminClient).GetConnectionInfo(...)
	C:/Users/runneradmin/go/pkg/mod/cloud.google.com/go/[email protected]/apiv1alpha/alloydb_admin_client.go:875
cloud.google.com/go/alloydbconn/internal/alloydb.fetchMetadata({0x140eae160, 0xc000385050}, 0xc0001d0960, {{0xc0002993e6, 0xa}, {0xc0002993f7, 0x9}, {0xc000299406, 0xa}, {0xc000299415, ...}})
	D:/a/alloydb-go-connector/alloydb-go-connector/internal/alloydb/refresh.go:62 +0x402
cloud.google.com/go/alloydbconn/internal/alloydb.refresher.performRefresh.func2()
	D:/a/alloydb-go-connector/alloydb-go-connector/internal/alloydb/refresh.go:238 +0x16d
created by cloud.google.com/go/alloydbconn/internal/alloydb.refresher.performRefresh in goroutine 38
	D:/a/alloydb-go-connector/alloydb-go-connector/internal/alloydb/refresh.go:236 +0x6cb
FAIL	cloud.google.com/go/alloydbconn/internal/alloydb	1.754s

[enocom]

Closing -- this seems to be an artifact of duplicate refreshes that we fixed in a release after this issue was opened.