summaryrefslogtreecommitdiff
path: root/buildscripts
diff options
context:
space:
mode:
authorTed Tuckman <ted.tuckman@mongodb.com>2019-03-15 15:12:58 -0400
committerTed Tuckman <ted.tuckman@mongodb.com>2019-03-18 12:51:05 -0400
commitc90d961fbe008f81455ceaf53a4c8284eb76bbc5 (patch)
treecf21bbe2ccf6f860d486a45206fdb16049fd8dac /buildscripts
parent5ab83a702659235ea138c62fca3e608bb1def8cf (diff)
downloadmongo-c90d961fbe008f81455ceaf53a4c8284eb76bbc5.tar.gz
SERVER-39781 Blacklist out_to_existing.js from continuous_config_stepdown
Diffstat (limited to 'buildscripts')
-rw-r--r--buildscripts/resmokeconfig/suites/sharding_continuous_config_stepdown.yml5
1 files changed, 5 insertions, 0 deletions
diff --git a/buildscripts/resmokeconfig/suites/sharding_continuous_config_stepdown.yml b/buildscripts/resmokeconfig/suites/sharding_continuous_config_stepdown.yml
index 0e23de1a080..06f8df00442 100644
--- a/buildscripts/resmokeconfig/suites/sharding_continuous_config_stepdown.yml
+++ b/buildscripts/resmokeconfig/suites/sharding_continuous_config_stepdown.yml
@@ -191,6 +191,11 @@ selector:
- jstests/sharding/out_fails_to_replace_sharded_collection.js
- jstests/sharding/out_stale_unique_key.js
- jstests/sharding/out_unique_key_requires_index.js
+ # In this suite the cluster may end up in a state where each shard believes the
+ # collection is sharded and the mongos believes it is unsharded. $out is not
+ # prepared to work correctly in this situation. This should be fixed by a future
+ # improvement in sharding infrastructure, and can be unblacklisted by SERVER-40172.
+ - jstests/sharding/out_to_existing.js
executor:
config: