[SERVER-59606] Do not set dynamic timeouts on tasks with tests that have no runtime history Created: 26/Aug/21 Updated: 29/Oct/23 Resolved: 26/Aug/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.4, 5.1.0-rc0 |
| 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: |
v5.0
|
||||||||
| Sprint: | DAG 2021-09-06 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 26 | ||||||||
| Story Points: | 1 | ||||||||
| Description |
|
When determining dynamic task timeouts, there is a case where a test may not have passed during our lookback window (2 weeks), but was run and still has a history. In this case, the reported runtime of the task looks like 0. If we hit this case, we should skip applying the dynamic timeout, since a runtime of 0 is inaccurate and we don't know what the actual runtime is. |
| Comments |
| Comment by Vivian Ge (Inactive) [ 06/Oct/21 ] |
|
Updating the fixversion since branching activities occurred yesterday. This ticket will be in rc0 when it’s been triggered. For more active release information, please keep an eye on #server-release. Thank you! |
| Comment by Githook User [ 20/Sep/21 ] |
|
Author: {'name': 'David Bradford', 'email': 'david.bradford@mongodb.com', 'username': 'dbradf'}Message: (cherry picked from commit c64f66f267f1af919f323a0d7a32292a9a0965d1) |
| Comment by Githook User [ 26/Aug/21 ] |
|
Author: {'name': 'David Bradford', 'email': 'david.bradford@mongodb.com', 'username': 'dbradf'}Message: |