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

v2/internal/proxy: TestCheckConnections failed #2206

Open
flaky-bot bot opened this issue Apr 28, 2024 · 2 comments
Open

v2/internal/proxy: TestCheckConnections failed #2206

flaky-bot bot opened this issue Apr 28, 2024 · 2 comments
Assignees
Labels
flakybot: flaky Tells the Flaky Bot not to close or comment on this issue. flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. 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.

Comments

@flaky-bot
Copy link

flaky-bot bot commented Apr 28, 2024

Note: #1884 was also for this test, but it was closed more than 10 days ago. So, I didn't mark it flaky.


commit: 54e65d1
buildURL: https://github.com/GoogleCloudPlatform/cloud-sql-proxy/actions/runs/8864322110
status: failed

@flaky-bot flaky-bot bot added flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. 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 Apr 28, 2024
Copy link
Author

flaky-bot bot commented Apr 28, 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 (54e65d1), this test passed in one build (https://github.com/GoogleCloudPlatform/cloud-sql-proxy/actions/runs/8864322110) and failed in another build (https://github.com/GoogleCloudPlatform/cloud-sql-proxy/actions/runs/8864322110).

@flaky-bot flaky-bot bot added the flakybot: flaky Tells the Flaky Bot not to close or comment on this issue. label Apr 28, 2024
@enocom
Copy link
Member

enocom commented Apr 30, 2024

=== RUN TestCheckConnections
2024/04/28 02:17:17 [proj:region:pg] Listening on 127.0.0.1:50000
2024/04/28 02:17:17 [proj:region:pg1] could not listen to address 127.0.0.1:60000: listen tcp 127.0.0.1:60000: bind: address already in use
proxy_test.go:669: proxy.NewClient error: [proj:region:pg1] Unable to mount socket: listen tcp 127.0.0.1:60000: bind: address already in use
--- FAIL: TestCheckConnections (0.00s)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flakybot: flaky Tells the Flaky Bot not to close or comment on this issue. flakybot: issue An issue filed by the Flaky Bot. Should not be added manually. 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.
Projects
None yet
Development

No branches or pull requests

2 participants