SERVER-26525: Factor out identical checkLog functions

1 files changed, 2 insertions, 18 deletions

diff --git a/jstests/sharding/config_version_rollback.js b/jstests/sharding/config_version_rollback.js
index 2fc5d78c8fc..bb066b8cc80 100644
--- a/jstests/sharding/config_version_rollback.js
+++ b/jstests/sharding/config_version_rollback.js
@@ -6,23 +6,7 @@
 
 (function() {
     "use strict";
-
-    // Wait for fail point message to be logged.
-    var checkLog = function(node, msg) {
-        assert.soon(
-            function() {
-                var logMessages = assert.commandWorked(node.adminCommand({getLog: 'global'})).log;
-                for (var i = 0; i < logMessages.length; i++) {
-                    if (logMessages[i].indexOf(msg) != -1) {
-                        return true;
-                    }
-                }
-                return false;
-            },
-            'Did not see a log entry for ' + node + ' containing the following message: ' + msg,
-            60000,
-            1000);
-    };
+    load("jstests/libs/check_log.js");
 
     // The config.version document is written on transition to primary. We need to ensure this
     // config.version document is rolled back for this test.
@@ -70,7 +54,7 @@
 
     // Ensure the primary is waiting to write the config.version document before stopping the oplog
     // fetcher on the secondaries.
-    checkLog(
+    checkLog.contains(
         origPriConn,
         'transition to primary - transitionToPrimaryHangBeforeInitializingConfigDatabase fail point enabled.');