[SERVER-44361] Fix timing in InitialSyncerTests Created: 01/Nov/19 Updated: 29/Oct/23 Resolved: 06/Nov/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matthew Russotto | Assignee: | Matthew Russotto |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Repl 2019-11-04, Repl 2019-11-18 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
The new cloners don't (and can't) use the NetworkInterfaceMock, and so don't run in lockstep with the unit test code. This results in the timing sometimes not being as the tests expect. We can use the cloner failpoints to synchronize the tests with the code under test. |
| Comments |
| Comment by Githook User [ 06/Nov/19 ] |
|
Author: {'name': 'Matthew Russotto', 'username': 'mtrussotto', 'email': 'matthew.russotto@mongodb.com'}Message: |