[SERVER-81146] Use historic runtime data to set default timeouts when the data is not full Created: 18/Sep/23 Updated: 29/Oct/23 Resolved: 21/Sep/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.0-rc0, 6.0.11, 7.0.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mikhail Shchatko | Assignee: | Mikhail Shchatko |
| 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: |
v7.0, v6.0
|
||||||||
| Sprint: | DAG 2023-10-02 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 44 | ||||||||
| Story Points: | 2 | ||||||||
| Description |
|
We are setting default timeouts when we don't have historic runtime data for at least one test. The current default timeout for non required builds in 2 hours, which is sometimes not enough. We can use partial historic runtime data to set default timeouts smarter then just using hardcoded values. |
| Comments |
| Comment by Githook User [ 22/Sep/23 ] |
|
Author: {'name': 'Mikhail Shchatko', 'email': 'mikhail.shchatko@mongodb.com', 'username': 'MikhailShchatko'}Message: (cherry picked from commit 79410907d1ff3ad614496713e6440c5e88991eed) |
| Comment by Githook User [ 22/Sep/23 ] |
|
Author: {'name': 'Mikhail Shchatko', 'email': 'mikhail.shchatko@mongodb.com', 'username': 'MikhailShchatko'}Message: (cherry picked from commit 79410907d1ff3ad614496713e6440c5e88991eed) |
| Comment by Githook User [ 21/Sep/23 ] |
|
Author: {'name': 'Mikhail Shchatko', 'email': 'mikhail.shchatko@mongodb.com', 'username': 'MikhailShchatko'}Message: |