diff options
| author | Matthew Russotto <matthew.russotto@10gen.com> | 2020-07-15 11:22:33 -0400 |
|---|---|---|
| committer | Evergreen Agent <no-reply@evergreen.mongodb.com> | 2020-07-15 19:40:56 +0000 |
| commit | c26b0c167e8db6506e547e1daaa51f09a6e6c1bd (patch) | |
| tree | 701c3403fcfc9444cb17dde260e4f9d1afaed528 | |
| parent | 1c3532ee1941e37f934f6c14bdc7786619d6b258 (diff) | |
| download | mongo-c26b0c167e8db6506e547e1daaa51f09a6e6c1bd.tar.gz | |
SERVER-49522 Exclude initial_sync_succeeds_when_syncing_node_removed.js from multiversion tests
| -rw-r--r-- | jstests/replsets/initial_sync_succeeds_when_syncing_node_removed.js | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/jstests/replsets/initial_sync_succeeds_when_syncing_node_removed.js b/jstests/replsets/initial_sync_succeeds_when_syncing_node_removed.js index 362c0e68a2a..8a0c0323aca 100644 --- a/jstests/replsets/initial_sync_succeeds_when_syncing_node_removed.js +++ b/jstests/replsets/initial_sync_succeeds_when_syncing_node_removed.js @@ -2,6 +2,8 @@ * Tests that initial sync will continue if the syncing node is removed during syncing. * This behavior is desired because transient DNS failures can cause the node to falsely believe * that it is removed. + * + * @tags: [requires_fcv_46] */ (function() { "use strict"; |