-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
DevProd Correctness
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
Ever since we upped the job count in burn_in to match the job count of the normal task it is derived from we have been hitting frequent cases of resource issues on the system running burn_in. There is currently no way to tune burn_in for tasks/tests without tuning the base task it is derived from. We should make a way to reduce job count for individual problematic tests.
Slack threads: https://mongodb.slack.com/archives/C0V79S1PY/p1739221078196369
https://mongodb.slack.com/archives/C0V79S1PY/p1740671760735599
- is related to
-
SERVER-101333 Investigate why burn_in tasks are generated with different distro
-
- Needs Scheduling
-
-
SERVER-99370 Apply resmoke job count correctly for burn-in tasks
-
- Closed
-