Repository navigation
Open
Labels
flakybot: flakyTells the Flaky Bot not to close or comment on this issue.Tells the Flaky Bot not to close or comment on this issue.flakybot: issueAn issue filed by the Flaky Bot. Should not be added manually.An issue filed by the Flaky Bot. Should not be added manually.priority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Description
Many tests failed at the same time in this package.
- I will close this issue when there are no more failures in this package and
there is at least one pass. - No new issues will be filed for this package until this issue is closed.
- If there are already issues for individual test cases, I will close them when
the corresponding test passes. You can close them earlier, if you prefer, and
I won't reopen them while this issue is still open.
Here are the tests that failed:
- TestFUSEREADME (v2/internal/proxy: TestFUSEREADME failed #2641)
- TestFUSEDialInstance/connecting_creates_intermediate_temp_directories (v2/internal/proxy: TestFUSEDialInstance failed #2642)
- TestFUSEAcceptErrorReturnedFromServe (v2/internal/proxy: TestFUSEAcceptErrorReturnedFromServe failed #2643)
- TestFUSEReadDir (v2/internal/proxy: TestFUSEReadDir failed #2644)
- TestLookupIgnoresContext (v2/internal/proxy: TestLookupIgnoresContext failed #2645)
- TestFUSEErrors (v2/internal/proxy: TestFUSEErrors failed #2646)
- TestFUSEWithBadInstanceName (v2/internal/proxy: TestFUSEWithBadInstanceName failed #2647)
- TestFUSECheckConnections (v2/internal/proxy: TestFUSECheckConnections failed #2648)
- TestFUSEClose (v2/internal/proxy: TestFUSEClose failed #2649)
- TestClientInitialization/with_incrementing_automatic_port_selection (v2/internal/proxy: TestClientInitialization failed #2550)
commit: e0935a5
buildURL: https://github.com/GoogleCloudPlatform/cloud-sql-proxy/actions/runs/31143184851
status: failed
Metadata
Metadata
Assignees
Labels
flakybot: flakyTells the Flaky Bot not to close or comment on this issue.Tells the Flaky Bot not to close or comment on this issue.flakybot: issueAn issue filed by the Flaky Bot. Should not be added manually.An issue filed by the Flaky Bot. Should not be added manually.priority: p2Moderately-important priority. Fix may not be included in next release.Moderately-important priority. Fix may not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Activity
flaky-bot commentedon Aug 7, 2026
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 (e0935a5), this test passed in one build (https://github.com/GoogleCloudPlatform/cloud-sql-proxy/actions/runs/31143184851) and failed in another build (https://github.com/GoogleCloudPlatform/cloud-sql-proxy/actions/runs/31143184851).