DRIVERS-2874: fix flaky maxConnecting-is-enforced CMAP test (#1563)

fix flaky maxConnecting-is-enforced CMAP test
mongodb · Apr 12, 2024 · 35aae1a · 35aae1a
1 parent 611b12c
commit 35aae1a
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 4 deletions.
diff --git a/...ion-monitoring-and-pooling/tests/cmap-format/pool-checkout-maxConnecting-is-enforced.json b/...ion-monitoring-and-pooling/tests/cmap-format/pool-checkout-maxConnecting-is-enforced.json
diff --git a/...tion-monitoring-and-pooling/tests/cmap-format/pool-checkout-maxConnecting-is-enforced.yml b/...tion-monitoring-and-pooling/tests/cmap-format/pool-checkout-maxConnecting-is-enforced.yml
@@ -13,7 +13,7 @@ failPoint:
     failCommands: ["isMaster","hello"]
     closeConnection: false
     blockConnection: true
-    blockTimeMS: 750
+    blockTimeMS: 800
 poolOptions:
   maxPoolSize: 10
   waitQueueTimeoutMS: 5000
@@ -36,7 +36,7 @@ operations:
     count: 1
   # wait some more time to ensure thread1 has begun establishing a Connection
   - name: wait
-    ms: 100
+    ms: 400
   # start 2 check out requests. Only one thread should
   # start creating a Connection and the other one should be
   # waiting for pendingConnectionCount to be less than maxConnecting,