summaryrefslogtreecommitdiff
path: root/jstests
diff options
context:
space:
mode:
authorWilliam Schultz <william.schultz@mongodb.com>2020-01-06 20:50:37 +0000
committerA. Jesse Jiryu Davis <jesse@mongodb.com>2020-01-27 15:37:58 -0500
commita5831bb58c14fcf7fe4cd665a774de87ea437561 (patch)
tree924b94ed77ccabbb5e0c7f803df7ca1630f4d576 /jstests
parenta59bcb9229b705ce830c5c77355b920650a4f199 (diff)
downloadmongo-a5831bb58c14fcf7fe4cd665a774de87ea437561.tar.gz
SERVER-43978 Blacklist stable_timestamp_can_advance_after_oplog_hole_abort.js from multiversion suites
Diffstat (limited to 'jstests')
-rw-r--r--jstests/replsets/stable_timestamp_can_advance_after_oplog_hole_abort.js2
1 files changed, 1 insertions, 1 deletions
diff --git a/jstests/replsets/stable_timestamp_can_advance_after_oplog_hole_abort.js b/jstests/replsets/stable_timestamp_can_advance_after_oplog_hole_abort.js
index af361887639..41a20e892c3 100644
--- a/jstests/replsets/stable_timestamp_can_advance_after_oplog_hole_abort.js
+++ b/jstests/replsets/stable_timestamp_can_advance_after_oplog_hole_abort.js
@@ -1,7 +1,7 @@
/**
* Test that the stable timestamp can advance after an oplog hole is released via an abort.
*
- * @tags: [uses_transactions]
+ * @tags: [uses_transactions,requires_fcv_44]
*/
(function() {