Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-35521

concurrency_simultaneous task shouldn't run against mobile storage engine

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0.0, 4.1.1
    • Component/s: Testing Infrastructure
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v4.0
    • Sprint:
      TIG 2018-06-18
    • Linked BF Score:
      0

      Description

      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.

        Attachments

          Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-32993 Mobile SE: Data inconsistencies with concurrent operations

          • Major - P3 - Major loss of function.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-29999 Implement FSM workload scheduler for concurrency_simultaneous task

          • Major - P3 - Major loss of function.
          • Closed

            Activity

              People

              Assignee:
              robert.guo Robert Guo
              Reporter:
              max.hirschhorn Max Hirschhorn
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: