Originally await_getmore_cmd was investigated as part of
SERVER-63019 ticket. However, the root cause of the slow run was not detected at that time.
The root cause for the await_getmore_cmd test running for too long was in the place where the document insert (that matches the predicate) should have woken up a waiting cursor in the getMore command. The issue is that the notification is fired when the write is done on the primary node (not on the majority of nodes), yet read concern is majority in the running suite. This causes the cursor to miss the documents upon being awaken and then will wait again till the timeout (which was specified previously to 10 minutes).
After discussing this issue with email@example.com we agreed on preserving the current behavior and disabling this part of the test in case the test is run with majority read concern.