[SERVER-40170] Increase the default timeout for unit-tests which schedule work through `NetworkTestEnv::launchAsync` Created: 15/Mar/19 Updated: 29/Oct/23 Resolved: 18/Mar/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.1.10, 4.0.27 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Kaloian Manassiev | Assignee: | Kaloian Manassiev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Backport Requested: |
v4.0
|
||||||||
| Sprint: | Sharding 2019-03-25 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 44 | ||||||||
| Description |
|
Unit-tests, which schedule asynchronous work through NetworkTestEnv::launchAsync currently wait for up to 15 seconds for that work to complete. On DEBUG builds and on slower Evergreen machine variants we have seen this async work take more than 15 seconds, causing the unit-tests to fail. In order to avoid these intermittent failures, we should increase this default timeout to be on the order of a few minutes (I'd say 5 minutes is a good round number). |
| Comments |
| Comment by Githook User [ 17/Aug/21 ] |
|
Author: {'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}Message: |
| Comment by Githook User [ 18/Mar/19 ] |
|
Author: {'name': 'Kaloian Manassiev', 'username': 'kaloianm', 'email': 'kaloian.manassiev@mongodb.com'}Message: |