Fixing test_execute_command_against_correct_db_on_background_health_check_determine_active_db_unhealthy

Author: petyaslavova

tests/test_asyncio/test_multidb/test_client.py

@@ -279,6 +279,14 @@ async def mock_check_health(database):
             async with MultiDBClient(mock_multi_db_config) as client:
                 assert await client.set("key", "value") == "OK1"
                 await error_event.wait()
+                # Wait for circuit breaker to actually open (not just the event)
+                max_retries = 10
+                for _ in range(max_retries):
+                    if mock_db1.circuit.state == CBState.OPEN:  # Circuit is open
+                        break
+                    await asyncio.sleep(0.01)
+
+                # Now the failover strategy will select mock_db2
                 assert await client.set("key", "value") == "OK2"
                 await asyncio.sleep(0.5)
                 assert await client.set("key", "value") == "OK1"

tests/test_multidb/test_client.py

@@ -268,6 +268,15 @@ def mock_check_health(database):
             client = MultiDBClient(mock_multi_db_config)
             assert client.set("key", "value") == "OK1"
             error_event.wait(timeout=0.5)
+
+            # Wait for circuit breaker to actually open (not just the event)
+            max_retries = 10
+            for _ in range(max_retries):
+                if mock_db1.circuit.state == CBState.OPEN:  # Circuit is open
+                    break
+                sleep(0.01)
+
+            # Now the failover strategy will select mock_db2
             assert client.set("key", "value") == "OK2"
             sleep(0.5)
             assert client.set("key", "value") == "OK1"