search

GoogleCloudPlatform / alloydb-auth-proxy

A utility for connecting securely to your AlloyDB instances
https://cloud.google.com/alloydb/docs/auth-proxy/overview?hl=hu
Apache License 2.0
58 stars 10 forks source link

internal/proxy: TestClientLimitsMaxConnections failed #551

Open flaky-bot[bot] opened 8 months ago

flaky-bot[bot] commented 8 months ago

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: 19d7ad969bce68d2b709e5f09f2bcf6869e224c5 buildURL: https://github.com/GoogleCloudPlatform/alloydb-auth-proxy/actions/runs/7550125554 status: failed

flaky-bot[bot] commented 8 months ago

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 (19d7ad969bce68d2b709e5f09f2bcf6869e224c5), this test passed in one build (https://github.com/GoogleCloudPlatform/alloydb-auth-proxy/actions/runs/7550125554) and failed in another build (https://github.com/GoogleCloudPlatform/alloydb-auth-proxy/actions/runs/7550125554).

enocom commented 5 months ago

=== RUN TestClientLimitsMaxConnections 2024/01/17 02:14:28 [proj.region.clust.inst] Listening on 127.0.0.1:5000 2024/01/17 02:14:28 [proj.region.clust.inst] accepted connection from 127.0.0.1:49207 2024/01/17 02:14:28 [proj.region.clust.inst] accepted connection from 127.0.0.1:49206 2024/01/17 02:14:28 max connections (1) exceeded, refusing new connection proxy_test.go:347: dial attempts did not match expected, want = 1, got = 0 --- FAIL: TestClientLimitsMaxConnections (0.00s)