-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Correctness
It's possible for an engineer to introduce a hook that uses the FileBasedThreadLifecycle object, and then forget to set TestData.useActionPermittedFile which instructs the FSM framework to create / delete the files required to coordinate the hook's actions with the tests.
When we forget to set the TestData useActionPermittedFile variable, the hook ends up doing nothing silently. This means we won't be getting the test coverage we think we're getting.
we should do away with the additional variable and get things to work without it. If that's not possible, we should add a linter / some other check that complains when a hook using the FileBasedThreadLifecycle is being run without the variable being set.
- is related to
-
SERVER-95248 Improve ContinuousAddRemoveShard's compatibility with FSM workloads
- Closed
- related to
-
SERVER-95380 Abstract away ThreadLifecycle object and get rid of the is_fsm_workload / use_action_permitted_file variable
- Needs Scheduling
-
SERVER-95417 Abstract away the concept of a background hook
- Needs Scheduling