cmd: TestPProfServer failed #238
Assignees
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
bot
added
priority: p2
|
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 (46d59c8), this test passed in one build (https://github.com/GoogleCloudPlatform/alloydb-auth-proxy/actions/runs/3964170164) and failed in another build (https://github.com/GoogleCloudPlatform/alloydb-auth-proxy/actions/runs/3964170164). |
This was referenced Jan 25, 2023
This was referenced Jan 27, 2023
|
Fixed in #252. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This test failed!
To configure my behavior, see the Flaky Bot documentation.
If I'm commenting on this issue too often, add the
flakybot: quietlabel andI will stop commenting.
commit: 46d59c8
buildURL: https://github.com/GoogleCloudPlatform/alloydb-auth-proxy/actions/runs/3964170164
status: failed
Test output
2023/01/20 02:26:39 The proxy has encountered a terminal error: unable to start: [proj.region.clust.inst] Unable to mount socket: 2023/01/20 02:26:39 SIGINT signal received. Shutting down... root_test.go:936: failed to dial endpoint: Get "http://localhost:9191/debug/pprof/": dial tcp [::1]:9191: connect: connection refusedThe text was updated successfully, but these errors were encountered: