[SERVER-45764] Generate resmoke tasks need to take setup time into account when setting timeouts Created: 24/Jan/20 Updated: 29/Oct/23 Resolved: 27/Jan/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.2.4, 4.3.4 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | David Bradford (Inactive) | Assignee: | Alexander Costas (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.2
|
||||
| Sprint: | DAG 2020-02-10 | ||||
| Participants: | |||||
| Story Points: | 1 | ||||
| Description |
|
When we generate timeouts in generate_resmoke_suites, we calculate the timeout to use based on the historic runtime of that tests being run. However, we fail to include any of the time spent running setup, including the time required to download the artifacts. We do include a buffer in the calculated timeouts, so we don't hit this too frequently. But that buffer is a lot smaller than we thought and any extra time spent setting up could cause the tests to hit timeouts even if the tests run at normal times. |
| Comments |
| Comment by Githook User [ 05/Feb/20 ] |
|
Author: {'name': 'Alexander Costas', 'username': 'ancostas', 'email': 'alexander.costas@mongodb.com'}Message: |
| Comment by Githook User [ 27/Jan/20 ] |
|
Author: {'email': 'alexander.costas@mongodb.com', 'username': 'ancostas', 'name': 'Alexander Costas'}Message: |
| Comment by David Bradford (Inactive) [ 24/Jan/20 ] |
|
It looks like adding a 5 minutes buffer to timeouts give setup enough time to run. |