SERVER-65166 Use compareOptimes in abort_in_progress_transactions_on_step_up.js

(cherry picked from commit e2bf96ccc04299feee022ee4fcdb0b6d6a0769d4)
(cherry picked from commit bfad9016db54c0cd5a12247abf01db3be81dcce2)

1 files changed, 7 insertions, 2 deletions

diff --git a/jstests/replsets/abort_in_progress_transactions_on_step_up.js b/jstests/replsets/abort_in_progress_transactions_on_step_up.js
index e58ede11577..669b5d81146 100644
--- a/jstests/replsets/abort_in_progress_transactions_on_step_up.js
+++ b/jstests/replsets/abort_in_progress_transactions_on_step_up.js
@@ -79,8 +79,13 @@ const startOpTime = testDB.getSiblingDB("local").oplog.rs.findOne({ts: commitOpT
 jsTestLog("Wait for the new primary to block on fail point.");
 stopReplProducerOnDocumentFailPoint.wait();
 
-jsTestLog("Wait for the new primary to apply the first op of transaction.");
-assert.soon(() => getLastOpTime(newPrimary) >= startOpTime);
+jsTestLog("Wait for the new primary to apply the first op of transaction at timestamp: " +
+          tojson(startOpTime));
+assert.soon(() => {
+    const lastOpTime = getLastOpTime(newPrimary);
+    jsTestLog("Current lastOpTime on the new primary: " + tojson(lastOpTime));
+    return rs.compareOpTimes(lastOpTime, startOpTime) >= 0;
+});
 
 // Now the transaction should be in-progress on newPrimary.
 txnTableEntry = getTxnTableEntry(newTestDB);