max_time_ms_does_not_leak_shard_cursor.js fails periodically (3% of evergreen runs), because there is an open cursor on shards after the mongoS query (correctly) failed with MaxTimeMSExpired. The test was added in 6.0 in response to SERVER-62710.

Possible solution idea: the remaining time is transferred from the cursor to the opCtx. Perhaps, the timeout should be removed from opCtx at the end of getMore.