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

Log when mock network interface is destroyed with outstanding requests

    • Fully Compatible
    • Query 2018-08-13

      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.

            Assignee:
            charlie.swanson@mongodb.com Charlie Swanson
            Reporter:
            charlie.swanson@mongodb.com Charlie Swanson
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: