[SERVER-84156] burn_in fails sometimes because it generates too many tasks Created: 13/Dec/23 Updated: 16/Jan/24 |
|
| Status: | Needs Scheduling |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Trevor Guidry | Assignee: | [DO NOT ASSIGN] Backlog - DevProd Correctness |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | FY25Q1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Correctness
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
In this task, burn_in failed because it tried to generate 200k+ tasks. By design burn_in generates a lot of tasks but 200k is unreasonable. At the time of writing this evergreen has a limit of 25k tasks per generation. We should try to aim under this limit. |