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

Log when mock network interface is destroyed with outstanding requests

    XMLWordPrintable

    Details

    • Backwards Compatibility:
      Fully Compatible
    • Sprint:
      Query 2018-08-13

      Description

      Tests which forget to schedule responses to remote commands triggered by the test can be hard to diagnose. For example, setting up the in-memory state representing a sharded collection requires mocking several responses to finds on the config servers. If you forget to schedule a response to one of them, it's hard to tell why the test is hung.

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: