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

After the first drop, assertSchemaMatch() should assert that subsequent drops succeed

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.6.3, 3.7.1
    • Component/s: Querying
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v3.6
    • Sprint:
      Query 2018-01-15
    • Linked BF Score:
      0

      Description

      In jstests/libs/assert_schema_match.js, we run several drop collections but don't assert that they succeed. We have to assert that they succeed for the second drop and onwards, otherwise state from the previous validation will linger and interferes with future assertions.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              tess.avitabile Tess Avitabile
              Reporter:
              kyle.suarez Kyle Suarez
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: