We have had at least 3 BFs recently (BF-44361, BF-44755, BF-45640) where the test timed out because a cursor left open by some operation pins range deletion from progressing until the cursor is reaped. SERVER-131725 was filed to prevent the root cause however until that is fixed any tests that use ShardingTest fixture and perform range deletions are affected.

cursorTimeoutMillis defaults to 10 minutes which is same as range deletion's helper that waits for the collection to be empty. We should either reduce cursorTimeoutMillis value for sharding tests or increase the time we wait for range deletions to complete.