From 9561ea73bc0004fc1835430f9789546484c1e7e7 Mon Sep 17 00:00:00 2001 From: Jacob Evans Date: Tue, 5 Nov 2019 19:45:39 +0000 Subject: SERVER-43749 Modernize mapReduce tests in core --- .../resmokeconfig/suites/sharded_collections_jscore_passthrough.yml | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) (limited to 'buildscripts/resmokeconfig/suites/sharded_collections_jscore_passthrough.yml') diff --git a/buildscripts/resmokeconfig/suites/sharded_collections_jscore_passthrough.yml b/buildscripts/resmokeconfig/suites/sharded_collections_jscore_passthrough.yml index 3f482a91acc..03e971ca184 100644 --- a/buildscripts/resmokeconfig/suites/sharded_collections_jscore_passthrough.yml +++ b/buildscripts/resmokeconfig/suites/sharded_collections_jscore_passthrough.yml @@ -76,9 +76,8 @@ selector: # TODO: Remove after fixing SERVER-32563. The implementation of explain for the count command is # incorrect on sharded collections. - jstests/core/explain_count.js - # TODO: Remove after fixing SERVER-14324. mapReduce behaves unpredictably when the out collection - # is sharded on anything other than {_id: 1}. - - jstests/core/mr_undef.js + # TODO: Remove after implementing SERVER-42677. Legacy mapReduce behaves unpredictably when the + # out collection is sharded on anything other than {_id: 1}. # TODO SERVER-32311: These tests use plan stage helpers which can't handle sharded explain output. - jstests/core/expr_index_use.js - jstests/core/index_multikey.js -- cgit v1.2.1