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

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.9.0
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • Repl 2021-02-08
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Matthew Russotto (Inactive)
            Reporter:
            Matthew Russotto (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: