[SERVER-47106] Selected tests doesn't limit the number of tasks to less than 1000 Created: 25/Mar/20 Updated: 27/Oct/23 Resolved: 30/Mar/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | James O'Leary | Assignee: | [DO NOT ASSIGN] Backlog - Decision Automation Group (DAG) (Inactive) |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Assigned Teams: |
Decision Automation Group
|
||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Description |
|
If a patch tries to generate over 1000 tasks, then it will be rejected by the evergreen api, causing a system failure:
|
| Comments |
| Comment by David Bradford (Inactive) [ 30/Mar/20 ] |
|
With evergreen increasing the task limit, this problem should be resolved. |
| Comment by David Bradford (Inactive) [ 25/Mar/20 ] |
|
It looks like the patch where we hit the limit was trying to generate a little move 1650 tasks. So, maybe 2000 for now. |
| Comment by David Bradford (Inactive) [ 25/Mar/20 ] |
|
For selected-tests, we are moving towards one task that generates the rest of the patch build (we are currently pulling in a few tasks statically, but there will only be 1 task that generates additional tasks). The total amount of configuration that is generated should be less than a full required patch build. It should only be run in patch builds. If it was run in a non-patch build, it would end up no-oping. Right now, we expect it to be run with a selected-tests alias. The alias pulling in the selected-tests task and a bunch of misc tasks (linters, concurrency suites, fuzzers, etc). |
| Comment by David Bradford (Inactive) [ 25/Mar/20 ] |
|
We should talk to evergreen to see if we can adjust the limit. It was previously a problem when several tasks were generating close to the limit. But in this case, we have one task generating several build variants so the limit probably doesn't make as much sense. brian.samek Any thoughts? |