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

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

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 3.6.3, 3.7.1
    • Affects Version/s: None
    • Component/s: Querying
    • None
    • Fully Compatible
    • ALL
    • v3.6
    • Query 2018-01-15
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            tess.avitabile@mongodb.com Tess Avitabile (Inactive)
            Reporter:
            kyle.suarez@mongodb.com Kyle Suarez (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved:
              None
              None
              None
              None