Created by: leontastic
This PR includes a test for processes being run sequentially after a job has been killed. It's failing right now because the same process thread is retained for queued jobs despite the previous iteration calling process.exit() within an async callback, causing subsequent jobs to die ungracefully and without warning. Possible solutions:
- Add a handler to restart jobs that exit in the middle of processing on a new thread
- Add a feature to kill jobs automatically upon completion, forcing a new thread to be retained every time
Depends on https://github.com/OptimalBits/bull/pull/749.