[Python] Fix flaky test test_sync_pubsub_exact_happy_path
#5057
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue link
This Pull Request is linked to issue (URL): #4970
Description
This PR addresses the flakiness observed in
TestSyncPubSub.test_sync_pubsub_exact_happy_path.In high-load environments (e.g., CI/CD), initializing two synchronous clients simultaneously occasionally results in a
ClosingError: connection attempt timed out.Solution
Implemented a retry mechanism in
tests/sync_tests/test_sync_pubsub.py.create_two_clients_with_pubsubcall in a retry loop.Verification
Verified that the test is more resilient to resource contention and transient network delays during client creation.