-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Correctness
Currently some background hooks have a variable use_action_permitted_file that needs to be set whenever an FSM workload is being run (note that this variable will be renamed to is_fsm_workload in SERVER-95248) - this variable determines what kind of lifecycle object is used in the hook.
When this variable isn't set in the suite's YAML file the result is that some tests become incompatible with the suite due to the hook running while the tests' setup() and teardown() methods are run.
Since Resmoke already has all the information necessary to know whether a suite is a concurrency suite or not, we should have Resmoke tell the hooks which lifecycle object to use instead. By doing this engineers won't have to think about the various lifecycle types that exist and can't make errors.
More context in comments.
- is related to
-
-
- Closed
-
-
-
- Closed
-
-
-
- Needs Scheduling
-
- related to
-
-
- Needs Scheduling
-