Closed MBartkowiakSTFC closed 2 weeks ago
The progress update and the terminate seem to kill most of the child processes.
However, it looks like there is still one more child process that it doesn't kill. Not sure if I needed to wait longer but I gave it a few minutes.
Also, I noticed that the MSD job goes to 100% then 0% then back to 100%. I guess this the multiprocessing version of #361.
This PR will be replaced by #471
Description of work At the moment, multicore jobs work, but do not report progress correctly, and cannot be aborted from the GUI. This PR adds a mechanism for aborting multicore jobs, and changes the way progress is reported for multicore jobs.
closes #447 closes #361
Fixes
To test Run a job using multiple cores. Check if the progress is updated correctly. Run a long job using multiple cores. Abort it before it finishes, and confirm that every child process terminates eventually, without being killed manually by the user. (For slower jobs this may take some time, but should happen eventually).