-
Type:
Improvement
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
DevProd Correctness
-
None
-
3
-
TBD
-
None
-
None
-
None
-
None
-
None
-
None
In response to SERVER-103438 we created this PR that moved core analysis to a standalone task outside of a display task. This has the benefit of not blocking the auto-reverter from running on a failing task until core analysis finishes.
There are other concerns that still need addressed regarding core analysis though:
1. Cost - the waste of money used for AWS machine
2. Evergreen availability - if evergreen is busy doing core analysis and we reach some threshold we won’t have enough machine available to do other work.
3. Patch time - The developer will get notified when a patch complete only when also the core analysis are completed. This can be a big productivity drag
It would be better still if we programmatically determined if core analysis actually needs to be ran for the specific failure case.
- is related to
-
SERVER-103438 Suites with "archive.tests = true" always trigger core dump analyzer on test failure
-
- Closed
-