Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

internal/proxy: TestClientLimitsMaxConnections failed #551

Open
flaky-bot bot opened this issue Jan 17, 2024 · 2 comments
Open

internal/proxy: TestClientLimitsMaxConnections failed #551

flaky-bot bot opened this issue Jan 17, 2024 · 2 comments
Assignees
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@flaky-bot
Copy link

flaky-bot bot commented Jan 17, 2024

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

@flaky-bot flaky-bot bot added flakybot: issue priority: p2 Moderately-important priority. Fix may not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. labels Jan 17, 2024
Copy link
Author

flaky-bot bot commented Jan 17, 2024

Looks like this issue is flaky. 😟

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

A human should fix and close this.


When run at the same commit (19d7ad9), 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
Copy link
Member

enocom commented Apr 8, 2024

=== 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)

@jackwotherspoon jackwotherspoon added priority: p3 Desirable enhancement or fix. May not be included in next release. and removed priority: p2 Moderately-important priority. Fix may not be included in next release. labels Jul 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p3 Desirable enhancement or fix. May not be included in next release. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

No branches or pull requests

2 participants