diff options
| author | Nicholas Zolnierz <nicholas.zolnierz@mongodb.com> | 2019-10-23 19:11:39 +0000 |
|---|---|---|
| committer | evergreen <evergreen@mongodb.com> | 2019-10-23 19:11:39 +0000 |
| commit | de524442c2ab683d31c942c6d0b3e84a6a2a3c65 (patch) | |
| tree | f368495496f84f0bda98e129463e09ce73cd285d /buildscripts/resmokeconfig/suites/concurrency_sharded_replication_with_balancer.yml | |
| parent | b11ca51de9765599b84e68156aedb26e27ef9b02 (diff) | |
| download | mongo-de524442c2ab683d31c942c6d0b3e84a6a2a3c65.tar.gz | |
SERVER-43303 Re introduce mapReduce fsm tests in sharded suites
Diffstat (limited to 'buildscripts/resmokeconfig/suites/concurrency_sharded_replication_with_balancer.yml')
| -rw-r--r-- | buildscripts/resmokeconfig/suites/concurrency_sharded_replication_with_balancer.yml | 11 |
1 files changed, 0 insertions, 11 deletions
diff --git a/buildscripts/resmokeconfig/suites/concurrency_sharded_replication_with_balancer.yml b/buildscripts/resmokeconfig/suites/concurrency_sharded_replication_with_balancer.yml index 5b8e6519f26..06f789f1c30 100644 --- a/buildscripts/resmokeconfig/suites/concurrency_sharded_replication_with_balancer.yml +++ b/buildscripts/resmokeconfig/suites/concurrency_sharded_replication_with_balancer.yml @@ -25,17 +25,6 @@ selector: - jstests/concurrency/fsm_workloads/agg_graph_lookup.js - jstests/concurrency/fsm_workloads/view_catalog_cycle_lookup.js - # Disabled due to SERVER-20057, 'Concurrent, sharded mapReduces can fail when temporary - # namespaces collide across mongos processes' - - jstests/concurrency/fsm_workloads/map_reduce_drop.js - - jstests/concurrency/fsm_workloads/map_reduce_inline.js - - jstests/concurrency/fsm_workloads/map_reduce_interrupt.js - - jstests/concurrency/fsm_workloads/map_reduce_merge.js - - jstests/concurrency/fsm_workloads/map_reduce_reduce.js - - jstests/concurrency/fsm_workloads/map_reduce_replace.js - - jstests/concurrency/fsm_workloads/map_reduce_replace_nonexistent.js - - jstests/concurrency/fsm_workloads/map_reduce_replace_remove.js - # Disabled due to MongoDB restrictions and/or workload restrictions # These workloads sometimes trigger 'Could not lock auth data update lock' |