We seem to quite frequently have an issue where node/python processes are left behind after a test run, usually due to a failing test. In our (IBM) CI, we just have a job we run before each flow that cleans up any node processes that might be lying around (there's a Unix version and a Windows version).
I feel like this is something that would be useful in CI, if we ran it as a job then it shouldn't interfere with build flows (as each machine only has one executor).
We seem to quite frequently have an issue where node/python processes are left behind after a test run, usually due to a failing test. In our (IBM) CI, we just have a job we run before each flow that cleans up any node processes that might be lying around (there's a Unix version and a Windows version).
I feel like this is something that would be useful in CI, if we ran it as a job then it shouldn't interfere with build flows (as each machine only has one executor).