[SERVER-40704] Have better task timeouts when dynamically setting the minimum Created: 17/Apr/19 Updated: 29/Oct/23 Resolved: 18/Apr/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.0.10, 4.1.11 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | David Bradford (Inactive) | Assignee: | David Bradford (Inactive) |
| 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 | ||||||||
| Backport Requested: |
v4.0
|
||||||||
| Sprint: | DAG 2019-04-22, DAG 2019-05-06 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 20 | ||||||||
| Description |
|
When resmoke tasks are split into sub-buckets, we will set a dynamic timeout that is 3 times how long we expect all the tests to execute. If all tests are really quick (a few seconds or less), small variations in test runtime can cause the timeout to be hit. To avoid this, we added a minimum timeout of 5 minutes. However, if the total runtime of the tests is close to that, we could still hit the timeout. If we are in a situation where the total runtime is less than the minimum, we should use 3 times the minimum to give us some extra buffer for variations in runtime. |
| Comments |
| Comment by Githook User [ 18/Apr/19 ] |
|
Author: {'name': 'David Bradford', 'username': 'dbradf', 'email': 'david.bradford@mongodb.com'}Message: (cherry picked from commit 233387efb49dc9403aa6c543191a19fc19c2c3b0) |
| Comment by Githook User [ 18/Apr/19 ] |
|
Author: {'email': 'david.bradford@mongodb.com', 'name': 'David Bradford', 'username': 'dbradf'}Message: |