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.

Sign up for GitHub

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

Jump to bottom

internal/proxy: TestRunConnectionCheck failed #685

Open
flaky-bot bot opened this issue Jul 31, 2024 · 2 comments
Open

internal/proxy: TestRunConnectionCheck failed #685

flaky-bot bot opened this issue Jul 31, 2024 · 2 comments
Assignees
@enocom
Labels
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 Jul 31, 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: 790b935
buildURL: https://github.com/GoogleCloudPlatform/alloydb-auth-proxy/actions/runs/10172804691
status: failed
@flaky-bot flaky-bot bot added 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. flakybot: issue labels Jul 31, 2024
@flaky-bot Flaky Bot
Copy link
Author

flaky-bot bot commented Jul 31, 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 (790b935), this test passed in one build (https://github.com/GoogleCloudPlatform/alloydb-auth-proxy/actions/runs/10172804691) and failed in another build (https://github.com/GoogleCloudPlatform/alloydb-auth-proxy/actions/runs/10172804691).

@enocom
Copy link
Member

enocom commented Jul 31, 2024

=== RUN TestRunConnectionCheck
proxy_test.go:693: proxy.NewClient error: [proj.region.clust.inst1] Unable to mount socket: listen tcp 127.0.0.1:50002: bind: An attempt was made to access a socket in a way forbidden by its access permissions.
--- FAIL: TestRunConnectionCheck (0.00s)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@enocom enocom

Labels
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
Milestone
No milestone
Development

No branches or pull requests
1 participant
@enocom