summaryrefslogtreecommitdiff
path: root/src/mongo/client/remote_command_retry_scheduler_test.cpp
diff options
context:
space:
mode:
Diffstat (limited to 'src/mongo/client/remote_command_retry_scheduler_test.cpp')
-rw-r--r--src/mongo/client/remote_command_retry_scheduler_test.cpp10
1 files changed, 5 insertions, 5 deletions
diff --git a/src/mongo/client/remote_command_retry_scheduler_test.cpp b/src/mongo/client/remote_command_retry_scheduler_test.cpp
index 3e3b3d3c513..c5eb97a381a 100644
--- a/src/mongo/client/remote_command_retry_scheduler_test.cpp
+++ b/src/mongo/client/remote_command_retry_scheduler_test.cpp
@@ -382,11 +382,11 @@ TEST_F(RemoteCommandRetrySchedulerTest, SchedulerIgnoresEmbeddedErrorInSuccessfu
// Scheduler does not parse document in a successful response for embedded errors.
// This is the case with some commands (e.g. find) which do not always return errors using the
// wire protocol.
- executor::RemoteCommandResponse response(BSON("ok" << 0 << "code"
- << int(ErrorCodes::FailedToParse) << "errmsg"
- << "injected error"),
- BSON("z" << 456),
- Milliseconds(100));
+ executor::RemoteCommandResponse response(
+ BSON("ok" << 0 << "code" << int(ErrorCodes::FailedToParse) << "errmsg"
+ << "injected error"),
+ BSON("z" << 456),
+ Milliseconds(100));
processNetworkResponse(response);
checkCompletionStatus(&scheduler, callback, response);