You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Additionally, this test requires drivers to set a fail point after an insertOne operation but before the subsequent retry.
240
240
* Drivers that are unable to set a failCommand after the CommandSucceededEvent SHOULD use mocking or write a unit test to cover the same sequence of events.
241
241
*
242
-
* 1. Create a client with retryWrites=true.
242
+
* Create a client with retryWrites=true.
243
243
*
244
-
* 2. Configure a fail point with error code `91` (ShutdownInProgress) with the `RetryableError` and
245
-
* `SystemOverloadedError` error labels:
244
+
* Configure a fail point with error code 91 (ShutdownInProgress):
* Drivers SHOULD only configure the 10107 fail point command if the the succeeded event is for the 91 error configured in step 2.
272
272
*
273
-
* Drivers SHOULD configure the second fail point command only if the event is for the first error configured in step 2.
274
-
*
275
-
* 4. Attempt an insertOne operation on any record for any database and collection. For the resulting error, assert that the associated error code is 91.
273
+
* Attempt an insertOne operation on any record for any database and collection. For the resulting error, assert that the associated error code is 91.
276
274
*/
277
275
it(
278
276
'when a retry attempt fails with an error labeled NoWritesPerformed, drivers MUST return the original error',
0 commit comments