summaryrefslogtreecommitdiff
path: root/buildscripts/resmokeconfig/suites/logical_session_cache_sharding_default_refresh_jscore_passthrough.yml
diff options
context:
space:
mode:
Diffstat (limited to 'buildscripts/resmokeconfig/suites/logical_session_cache_sharding_default_refresh_jscore_passthrough.yml')
-rw-r--r--buildscripts/resmokeconfig/suites/logical_session_cache_sharding_default_refresh_jscore_passthrough.yml5
1 files changed, 2 insertions, 3 deletions
diff --git a/buildscripts/resmokeconfig/suites/logical_session_cache_sharding_default_refresh_jscore_passthrough.yml b/buildscripts/resmokeconfig/suites/logical_session_cache_sharding_default_refresh_jscore_passthrough.yml
index dbd0948dac7..34bfad07835 100644
--- a/buildscripts/resmokeconfig/suites/logical_session_cache_sharding_default_refresh_jscore_passthrough.yml
+++ b/buildscripts/resmokeconfig/suites/logical_session_cache_sharding_default_refresh_jscore_passthrough.yml
@@ -81,9 +81,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