Split jscore tests that run mapReduce but do not specifically test mapReduce into two

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.2.0-rc2, 4.3.1
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • v4.2
    • Repl 2019-06-03, Repl 2019-06-17
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      SERVER-40938 banned afterClusterTime in dbHash and mapReduce. As a result, dbHash and mapReduce are no longer able to run in causally consistent sessions. Jscore tests that run mapReduce were tagged with does_not_support__causal_consistency and were excluded from causal consistent passthroughs.

      There are 17 tests that were tagged but do not specifically test mapReduce. We want to untag these tests and split these tests into a mapReduce and non-mapReduce section and only blacklist the mapReduce section so we can gain test coverage back.

      jstests/core/bypass_doc_validation.js
      jstests/core/collation.js
      jstests/core/commands_namespace_parsing.js
      jstests/core/commands_that_do_not_write_do_not_accept_wc.js
      jstests/core/constructors.js
      jstests/core/expr.js
      jstests/core/function_string_representations.js
      jstests/core/geo_big_polygon3.js
      jstests/core/index_stats.js
      jstests/core/opcounters_active.js
      jstests/core/or4.js
      jstests/core/recursion.js
      jstests/core/system_profile.js
      jstests/core/temp_cleanup.js
      jstests/core/txns/commands_banning_txnnumber_outside_transactions.js
      jstests/core/txns/commands_not_allowed_in_txn.js
      jstests/core/views/views_all_commands.js

            Assignee:
            Allison Easton
            Reporter:
            Lingzhi Deng
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: