1 files changed, 0 insertions, 86 deletions
diff --git a/jstests/core/killop.js b/jstests/core/killop.js
deleted file mode 100644
index 845e60bb74f..00000000000
--- a/jstests/core/killop.js
+++ /dev/null
@@ -1,86 +0,0 @@
-/**
- * Basic test of killop functionality.
- *
- * Theory of operation: Creates two operations that will take a long time, sends killop for those
- * operations, and then attempts to infer that the operations died because of killop, and not for
- * some other reason.
- *
- * NOTES:
- * The long operations are count({ $where: function() { while (1) { sleep(500); } } }).  These
- * operations do not terminate until the server determines that they've spent too much time in JS
- * execution, typically after 30 seconds of wall clock time have passed.  For these operations to
- * take a long time, the counted collection must not be empty; hence an initial write to the
- * collection is required.
- */
-(function() {
-    'use strict';
-
-    if (jsTest.options().storageEngine === "mmapv1" && db.isMaster().msg === "isdbgrid") {
-        // SERVER-10747 MMAPv1's journal thread can block behind a long-running and non-yielding
-        // $where operations. This causes subsequent operations on the collection, such as
-        // setShardVersion, to block behind MMAPv1's journal thread.  We therefore cannot expect
-        // to always be able to see *both* count operations running on a shard at the same time.
-        jsTest.log("Skipping test when running in a sharded cluster with mmapv1 shards");
-        return;
-    }
-
-    var t = db.jstests_killop;
-    t.save({x: 1});
-
-    /**
-     * This function filters for the operations that we're looking for, based on their state and
-     * the contents of their query object.
-     */
-    function findRelevantOps(curops) {
-        var ids = [];
-        for (var i in curops) {
-            var o = curops[i];
-            // We *can't* check for ns, b/c it's not guaranteed to be there unless the query is
-            // active, which it may not be in our polling cycle - particularly b/c we sleep every
-            // second in both the query and the assert
-            if ((o.active || o.waitingForLock) && o.query && o.query.query &&
-                o.query.query.$where && o.query.count == "jstests_killop") {
-                ids.push(o.opid);
-            }
-        }
-        return ids;
-    }
-
-    var countWithWhereOp =
-        'db.jstests_killop.count({ $where: function() { while (1) { sleep(500); } } });';
-
-    jsTestLog("Starting long-running $where operation");
-    var s1 = startParallelShell(countWithWhereOp);
-    var s2 = startParallelShell(countWithWhereOp);
-
-    jsTestLog("Finding ops in currentOp() output");
-    var allOps;
-    var relevantOps = [];
-    assert.soon(
-        function() {
-            allOps = db.currentOp().inprog;
-            relevantOps = findRelevantOps(allOps);
-            return relevantOps.length == 2;
-        },
-        function() {
-            return tojson(allOps);
-        },
-        60000);
-
-    var start = new Date();
-    jsTestLog("Killing ops");
-    db.killOp(relevantOps[0]);
-    db.killOp(relevantOps[1]);
-
-    jsTestLog("Waiting for ops to terminate");
-    [s1, s2].forEach(function(awaitShell) {
-        var exitCode = awaitShell({checkExitSuccess: false});
-        assert.neq(
-            0, exitCode, "expected shell to exit abnormally due to JS execution being terminated");
-    });
-
-    // don't want to pass if timeout killed the js function.
-    var end = new Date();
-    var diff = end - start;
-    assert.lt(diff, 30000, "Start: " + start + "; end: " + end + "; diff: " + diff);
-})();