Summary

"maxTimeMS value in the command is less than timeoutMS" test in command-execution.yml CSOT test file is flaky due to overly restrictive time allowed for driver to accumulate heartbeats 

Motivation

Who is the affected end user?

Driver Engineers

How does this affect the end user?

N/A

How likely is it that this problem or use case will occur?

Likely for some drivers

If the problem does occur, what are the consequences and how severe are they?

Flaky tests

Is this issue urgent?

No

Is this ticket required by a downstream team?

No

Is this ticket only for tests?

Just test changes

Acceptance Criteria

Increase wait time to allow drivers to accumulate enough heartbeats and accurately set their roundTripTime values in order to short-circuit operations according to CSOT spec.