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

cmd: TestQuitQuitQuitGet failed #743

Closed
flaky-bot bot opened this issue Jan 1, 2025 · 3 comments
Closed

cmd: TestQuitQuitQuitGet failed #743

flaky-bot bot opened this issue Jan 1, 2025 · 3 comments
Assignees
Labels
flakybot: flaky 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.

Comments

@flaky-bot
Copy link

flaky-bot bot commented Jan 1, 2025

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: 3e44db8
buildURL: https://github.com/GoogleCloudPlatform/alloydb-auth-proxy/actions/runs/12566285108
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 Jan 1, 2025
Copy link
Author

flaky-bot bot commented Jan 2, 2025

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

@enocom
Copy link
Member

enocom commented Jan 2, 2025

=== RUN TestQuitQuitQuitGet
2025/01/01 02:29:57 [proj.region.clust.inst] Listening on 127.0.0.1:5432
2025/01/01 02:29:57 The proxy has started successfully and is ready for new connections!
2025/01/01 02:29:57 Enabling quitquitquit endpoint at localhost:9192
2025/01/01 02:29:57 The proxy has encountered a terminal error: failed to start HTTP server: listen tcp 127.0.0.1:9192: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted.
root_test.go:1260: failed to dial endpoint: Get "http://localhost:9192/quitquitquit": dial tcp [::1]:9192: connectex: No connection could be made because the target machine actively refused it.
--- FAIL: TestQuitQuitQuitGet (11.03s)

@enocom
Copy link
Member

enocom commented Jan 2, 2025

Duplicate of #739.

@enocom enocom closed this as completed Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flakybot: flaky 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.
Projects
None yet
Development

No branches or pull requests

1 participant