diff --git a/source/transactions/tests/unified/error-labels-blockConnection.json b/source/transactions/tests/unified/error-labels-blockConnection.json index 8da04d1005..60d753edce 100644 --- a/source/transactions/tests/unified/error-labels-blockConnection.json +++ b/source/transactions/tests/unified/error-labels-blockConnection.json @@ -12,6 +12,12 @@ } ], "createEntities": [ + { + "client": { + "id": "failPointClient", + "useMultipleMongoses": false + } + }, { "client": { "id": "client0", @@ -60,7 +66,7 @@ "object": "testRunner", "name": "failPoint", "arguments": { - "client": "client0", + "client": "failPointClient", "failPoint": { "configureFailPoint": "failCommand", "mode": { diff --git a/source/transactions/tests/unified/error-labels-blockConnection.yml b/source/transactions/tests/unified/error-labels-blockConnection.yml index 7fed7fc92b..132c908a50 100644 --- a/source/transactions/tests/unified/error-labels-blockConnection.yml +++ b/source/transactions/tests/unified/error-labels-blockConnection.yml @@ -17,6 +17,10 @@ runOnRequirements: - load-balanced createEntities: + - + client: + id: &failPointClient failPointClient + useMultipleMongoses: false - client: id: &client0 client0 @@ -60,7 +64,7 @@ tests: object: testRunner name: failPoint arguments: - client: *client0 + client: *failPointClient failPoint: # Drivers stop retrying after two socket timeouts that occur due to the use of socketTimeoutMS configureFailPoint: failCommand diff --git a/source/unified-test-format/unified-test-format.md b/source/unified-test-format/unified-test-format.md index 1c28c46058..69df90b12d 100644 --- a/source/unified-test-format/unified-test-format.md +++ b/source/unified-test-format/unified-test-format.md @@ -2002,6 +2002,11 @@ The following arguments are supported: lead to unpredictable behavior if different servers were selected for configuring the fail point and executing subsequent operations. + When configuring a fail point, a test MUST NOT use a client entity that specifies timeout options such as + `socketTimeoutMS` in `uriOptions`. Since the test runner disables the fail point using the same client after the + test, short timeouts can cause the cleanup to fail intermittently. Tests that need a client with timeout options + MUST configure the fail point using a separate client entity without them. + When executing this operation, the test runner MUST keep a record of the fail point so that it can be disabled after the test. The test runner MUST also ensure that the `configureFailPoint` command is excluded from the list of observed command monitoring events for this client (if applicable). @@ -3470,6 +3475,8 @@ other specs *and* collating spec changes developed in parallel or during the sam ## Changelog +- 2026-10-29: Require that fail points not be configured through clients with timeout options. + - 2026-08-26: **Schema version 1.29.** Introduced the `$$gte` operator, the lower-bound counterpart to `$$lte`. Also clarified that `ignoreExtraSpans`