Currently, the test sets the batchSizeLimit to 2 and expects that we hang after applying one batch (ie. applying 2 of the 3 insert entries here). However, it seems possible that a resumeToken oplog entry finds its way into the batch, which causes our expectations of the batch contents and the number of no-op oplog entries to be applied to be incorrect.