[SERVER-46732] Cap number of tasks generated on non-required build variants Created: 09/Mar/20 Updated: 29/Oct/23 Resolved: 10/Mar/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Testing Infrastructure |
| Affects Version/s: | None |
| Fix Version/s: | 4.4.0-rc0, 4.7.0 |
| 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.4
|
||||
| Sprint: | DAG 2020-03-23 | ||||
| Participants: | |||||
| Story Points: | 1 | ||||
| Description |
|
We recently hit an issue where the amount of evergreen project config generated by generate.tasks exceeded the maximum document size and started causing issues. It looks like this was caused by the number of tasks being generated as each task adds to the project config. It also looks like this would only happen if all the build variants in the version were run. We could reduce the chance of this happening by capping the number of sub-tasks we will generate for a task in non-required build variants. As a server engineer, AC:
|
| Comments |
| Comment by Githook User [ 10/Mar/20 ] |
|
Author: {'username': 'dbradf', 'name': 'David Bradford', 'email': 'david.bradford@mongodb.com'}Message: (cherry picked from commit 62c56c44fb107c2ff34a0752e8f254b263e4f630) |
| Comment by Githook User [ 09/Mar/20 ] |
|
Author: {'username': 'dbradf', 'name': 'David Bradford', 'email': 'david.bradford@mongodb.com'}Message: |