[SERVER-41295] Add timeouts to burn_in generated tasks Created: 23/May/19 Updated: 29/Oct/23 Resolved: 01/Jul/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.1 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | David Bradford (Inactive) | Assignee: | Lydia Stepanek (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 | ||||
| Sprint: | DAG 2019-06-17, DAG 2019-07-01, DAG 2019-07-15 | ||||
| Participants: | |||||
| Linked BF Score: | 25 | ||||
| Story Points: | 2 | ||||
| Description |
|
Since we do not explicitly set a timeout for burn_in generated tasks, a hung test would not fail until the default timeout is hit. This has lead to some timeouts causing large log files to be written and makes it difficult to access the log files. If a given test has test history, we should be able to get an approximation of how long the test should run for and set timeouts dynamically. The "generate_resmoke_tasks" already does this. As a server engineer, AC:
|
| Comments |
| Comment by Githook User [ 01/Jul/19 ] |
|
Author: {'name': 'Lydia Stepanek', 'email': 'lydia.stepanek@mongodb.com', 'username': 'lydiastepanek'}Message: |
| Comment by Lydia Stepanek (Inactive) [ 18/Jun/19 ] |