[SERVER-36383] Log when mock network interface is destroyed with outstanding requests Created: 31/Jul/18 Updated: 29/Oct/23 Resolved: 01/Aug/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code, Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.2 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Charlie Swanson | Assignee: | Charlie Swanson |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Query 2018-08-13 |
| Participants: |
| 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. |
| Comments |
| Comment by Githook User [ 01/Aug/18 ] |
|
Author: {'username': 'cswanson310', 'name': 'Charlie Swanson', 'email': 'charlie.swanson@mongodb.com'}Message: |