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

Oplog fetcher mock needs to delay its destruction until it is no longer being called from the test

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.9.0
    • None
    • Replication
    • None
    • Fully Compatible
    • ALL
    • Repl 2021-02-08
    • 0

    Description

      The test code may have an unowned reference to the OplogFetcherMock. If the mock is destroyed while the test code is enqueuing a batch (e.g. because the batch is invalid), the test will crash. We should delay destruction of the mock until the call is finished.

      Making sure the unowned reference remains valid between calls is up to the test code itself, however.

      Attachments

        Activity

          People

            matthew.russotto@mongodb.com Matthew Russotto
            matthew.russotto@mongodb.com Matthew Russotto
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: