summaryrefslogtreecommitdiff
path: root/jstests/core/killop_drop_collection.js
diff options
context:
space:
mode:
authorHenrik Edin <henrik.edin@mongodb.com>2018-04-11 14:09:01 -0400
committerHenrik Edin <henrik.edin@mongodb.com>2018-04-18 09:14:20 -0400
commit1a4017efa471bd9f242daf436d3560fb83bacc27 (patch)
tree7834792811ea63b4705b54ba5a57a6ca8ecb6c40 /jstests/core/killop_drop_collection.js
parent46e2583c36856e0d377fcb35f2208a0ac516f031 (diff)
downloadmongo-1a4017efa471bd9f242daf436d3560fb83bacc27.tar.gz
SERVER-29725 Tag jstests in core so we can run the suite on mongoe.
Diffstat (limited to 'jstests/core/killop_drop_collection.js')
-rw-r--r--jstests/core/killop_drop_collection.js8
1 files changed, 8 insertions, 0 deletions
diff --git a/jstests/core/killop_drop_collection.js b/jstests/core/killop_drop_collection.js
index 53265010bf8..d21b81fe600 100644
--- a/jstests/core/killop_drop_collection.js
+++ b/jstests/core/killop_drop_collection.js
@@ -3,6 +3,14 @@
* to complete. Interrupting a collection drop could leave the database in an inconsistent state.
* This test confirms that killOp won't interrupt a collection drop, and that the drop occurs
* successfully.
+ *
+ * @tags: [
+ * # killop command is not yet available on embedded
+ * incompatible_with_embedded_todo_investigate,
+ *
+ * # Uses index building in background
+ * requires_background_index,
+ * ]
*/
(function() {
"use strict";