[SERVER-43288] Update fallback values for generated tasks Created: 11/Sep/19 Updated: 29/Oct/23 Resolved: 13/Sep/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.2.1, 4.3.1 |
| Type: | Improvement | 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 | ||||
| Backport Requested: |
v4.2
|
||||
| Sprint: | DAG 2019-09-23 | ||||
| Participants: | |||||
| Story Points: | 2 | ||||
| Description |
|
The cached historic test results have been turned off in evergreen for the past few weeks. This has lead to generated tasks not being able to use runtime to split up the tasks. All tasks have a fallback value to use to split tasks if there isn't historic data, but some of those value are set to 1 and are causing timeouts. For example, we should do a pass through all the suites and make sure the fallback values are appropriate. As a server engineer, AC:
|
| Comments |
| Comment by Githook User [ 13/Sep/19 ] |
|
Author: {'username': 'dbradf', 'email': 'david.bradford@mongodb.com', 'name': 'David Bradford'}Message: (cherry picked from commit 83005792b502eceb719653179ef6e283ecf52ef1) |
| Comment by Githook User [ 13/Sep/19 ] |
|
Author: {'name': 'David Bradford', 'username': 'dbradf', 'email': 'david.bradford@mongodb.com'}Message: |