summaryrefslogtreecommitdiff
path: root/buildscripts
diff options
context:
space:
mode:
authorDianna Hohensee <dianna.hohensee@10gen.com>2016-01-13 17:30:00 -0500
committerDianna Hohensee <dianna.hohensee@10gen.com>2016-01-15 16:18:05 -0500
commit920d38ceb07bff0ec18e2f173d942c3b743dea4b (patch)
tree9643000f53c9fdd8769404c5a43df3b3beb1274c /buildscripts
parent2d8008289b9d075c56841dc08830bb7cff28aeaf (diff)
downloadmongo-920d38ceb07bff0ec18e2f173d942c3b743dea4b.tar.gz
SERVER-22081 blacklisting tests from the continuous config stepdown suite that do direct writes (with no retries) against config/admin databases
Diffstat (limited to 'buildscripts')
-rw-r--r--buildscripts/resmokeconfig/suites/sharding_continuous_config_stepdown.yml13
1 files changed, 13 insertions, 0 deletions
diff --git a/buildscripts/resmokeconfig/suites/sharding_continuous_config_stepdown.yml b/buildscripts/resmokeconfig/suites/sharding_continuous_config_stepdown.yml
index 2046d837a33..01f4d3ff7ac 100644
--- a/buildscripts/resmokeconfig/suites/sharding_continuous_config_stepdown.yml
+++ b/buildscripts/resmokeconfig/suites/sharding_continuous_config_stepdown.yml
@@ -64,6 +64,16 @@ selector:
- jstests/sharding/top_chunk_autosplit.js
- jstests/sharding/count_config_servers.js
- jstests/sharding/conf_server_write_concern.js
+ # No retries on direct writes to the config/admin databases on the config servers
+ - jstests/sharding/listDatabases.js
+ - jstests/sharding/bulk_insert.js
+ - jstests/sharding/printShardingStatus.js
+ # Balancer writes (direct write to config database with no retries)
+ - jstests/sharding/remove2.js
+ - jstests/sharding/auto2.js
+ - jstests/sharding/features3.js
+ - jstests/sharding/in_memory_sort_limit.js
+ - jstests/sharding/parallel.js
# Calls the config server primary directly (not through mongos)
- jstests/sharding/moveprimary_ignore_sharded.js
- jstests/sharding/min_optime_recovery.js
@@ -80,6 +90,9 @@ selector:
- jstests/sharding/startup_with_all_configs_down.js
- jstests/sharding/replset_config/lagged_config_secondary.js
- jstests/sharding/replset_config/autodiscover_config_rs_from_secondary.js
+ - jstests/sharding/sharding_state_after_stepdown.js
+ - jstests/sharding/rs_stepdown_and_pooling.js
+ - jstests/sharding/mongos_no_replica_set_refresh.js
# Nothing is affected by config server step down
- jstests/sharding/replset_config/basic_sharding_params.js
# ShardingTest is never used, so continuous step down thread never starts