concurrency_simultaneous task shouldn't run against mobile storage engine

XMLWordPrintableJSON

    • Fully Compatible
    • v4.0
    • TIG 2018-06-18
    • 0
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      SERVER-32993 still needs to be investigated before the concurrency and concurrency_simultaneous Evergreen tasks can be reenabled. The blacklisting of the concurrency_simultaneous.yml test suite got lost when converting it from running fsm_all_simultaneous.js to running groups of FSM workloads directly via resmoke.py as part of SERVER-29999.

              Assignee:
              Robert Guo (Inactive)
              Reporter:
              Max Hirschhorn
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: