You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When ipcluster is running and you hit Control-C, it should stop all of its child processes and then exit. On Windows, under Python 2.6, doing Control-C exits immediately and doesn't stop the child processes. When using the WinbHPC scheduler, these child processe are job.exe. When I add --log-level 10 to ipcluster and then retry, I see that it looks like the job.exe processes have already exited. This could be a tough one to track down and the problem could even be in Twisted.
The text was updated successfully, but these errors were encountered:
Original Launchpad bug 515376: https://bugs.launchpad.net/ipython/+bug/515376
Reported by: ellisonbg (Brian Granger).
When ipcluster is running and you hit Control-C, it should stop all of its child processes and then exit. On Windows, under Python 2.6, doing Control-C exits immediately and doesn't stop the child processes. When using the WinbHPC scheduler, these child processe are job.exe. When I add --log-level 10 to ipcluster and then retry, I see that it looks like the job.exe processes have already exited. This could be a tough one to track down and the problem could even be in Twisted.
The text was updated successfully, but these errors were encountered: