In BF-26761 and BF-26762, allow_partial_results_with_maxTimeMS_failpoints.js runs some find queries with a maxTimeMS timeout of only 30ms or 40ms, which does not leave enough margin for delays due to resource contention. This is controlled via the ampleTimeMS variable, which was being set to 10x the runtime of some query. When I wrote the test and tested locally, I was seeing ampleTimeMS values around 5 seconds. Evergreen environments are just a lot faster in some cases (probably due to using optimized instead of debug builds).

To make this test more robust, and hopefully address those BFs, we should lower-bound ampleTimeMS with some more conservative value, like one second.