[issue19675] Pool dies with excessive workers, but does not cleanup

2018-11-05 Thread Julien Palard
Change by Julien Palard : -- resolution: -> fixed stage: patch review -> resolved status: open -> closed ___ Python tracker ___

[issue19675] Pool dies with excessive workers, but does not cleanup

2018-11-04 Thread ppperry
Change by ppperry : -- nosy: -ppperry ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue19675] Pool dies with excessive workers, but does not cleanup

2018-11-04 Thread Julien Palard
Julien Palard added the comment: New changeset 5d236cafd7126e640fb25541fcc7e0a494450143 by Julien Palard in branch 'master': bpo-19675: Terminate processes if construction of a pool is failing. (GH-5614) https://github.com/python/cpython/commit/5d236cafd7126e640fb25541fcc7e0a494450143

[issue19675] Pool dies with excessive workers, but does not cleanup

2018-02-10 Thread Julien Palard
Change by Julien Palard : -- pull_requests: +5424 stage: -> patch review ___ Python tracker ___

[issue19675] Pool dies with excessive workers, but does not cleanup

2017-03-13 Thread ppperry
ppperry added the comment: Can't you just mock the Process class to have a start method that always raises an error? -- nosy: +ppperry ___ Python tracker

[issue19675] Pool dies with excessive workers, but does not cleanup

2017-02-17 Thread Camilla Montonen
Camilla Montonen added the comment: Would it be possible to see a review of the existing attempts at testing this issue? -- ___ Python tracker ___

[issue19675] Pool dies with excessive workers, but does not cleanup

2017-02-14 Thread Dustin Oprea
Dustin Oprea added the comment: I don't think this can be tested. Throwing exceptions in the remote process causes exceptions that can't be caught in the same way (when the initializer fails the pool just attempts to recreate the process over and over) and I don't think it'd be acceptable to

[issue19675] Pool dies with excessive workers, but does not cleanup

2017-02-13 Thread Davin Potts
Davin Potts added the comment: For triggering the exception, supplying a Process target that deliberately fails sounds right. As for tests for the various start methods (fork/forkserver/spawn), if you are looking at the 3.x branches you'll find this was been consolidated so that one test

[issue19675] Pool dies with excessive workers, but does not cleanup

2017-02-13 Thread Dustin Oprea
Dustin Oprea added the comment: Okay. Thanks for weighing-in. I'm trying to figure out how to write the tests. The existing set of tests for multiprocessing is a near nightmare. It seems like I might have to use one of the existing "source code" definitions to test for the no-cleanup

[issue19675] Pool dies with excessive workers, but does not cleanup

2017-02-13 Thread Davin Potts
Davin Potts added the comment: @Winterflower: Thank you for encouraging @dsoprea to create the new PR and working to convert the previous patch. @dsoprea: Thank you for taking the time to create the PR especially after this has been sitting unloved for so long. Though the new workflow using

[issue19675] Pool dies with excessive workers, but does not cleanup

2017-02-13 Thread Davin Potts
Changes by Davin Potts : -- versions: +Python 2.7, Python 3.7 ___ Python tracker ___

[issue19675] Pool dies with excessive workers, but does not cleanup

2017-02-12 Thread Dustin Oprea
Dustin Oprea added the comment: https://github.com/python/cpython/pull/57 On Sun, Feb 12, 2017 at 5:29 PM, Camilla Montonen wrote: > > Camilla Montonen added the comment: > > @dsoprea: would you like to open a PR for this issue on Github? if not, > are you happy for me

[issue19675] Pool dies with excessive workers, but does not cleanup

2017-02-12 Thread Camilla Montonen
Camilla Montonen added the comment: @dsoprea: would you like to open a PR for this issue on Github? if not, are you happy for me to do it? -- ___ Python tracker

[issue19675] Pool dies with excessive workers, but does not cleanup

2017-02-12 Thread Camilla Montonen
Camilla Montonen added the comment: I've reformatted Dustin Oprea's original patch to be compatible with git, applied it to master and executed _test_multiprocessing suite. All tests pass locally. -- Added file: http://bugs.python.org/file46635/bug19675git.patch

[issue19675] Pool dies with excessive workers, but does not cleanup

2017-02-11 Thread Camilla Montonen
Changes by Camilla Montonen : -- nosy: +Winterflower ___ Python tracker ___ ___

[issue19675] Pool dies with excessive workers, but does not cleanup

2017-02-07 Thread Ned Deily
Changes by Ned Deily : -- nosy: +davin ___ Python tracker ___ ___ Python-bugs-list mailing

[issue19675] Pool dies with excessive workers, but does not cleanup

2017-02-07 Thread Vladimir Feinberg
Vladimir Feinberg added the comment: I'm still hitting this issue in Python 3.6.0 :: Anaconda 4.3.0 (64-bit). Is there a reason this patch has been ignored? This is on CentOS release 6.5 -- nosy: +Vladimir Feinberg versions: +Python 3.6 -Python 2.7, Python 3.3 Added file:

[issue19675] Pool dies with excessive workers, but does not cleanup

2013-11-20 Thread Dustin Oprea
New submission from Dustin Oprea: If you provide a number of processes to a Pool that the OS can't fulfill, Pool will raise an OSError and die, but does not cleanup any of the processes that it has forked. This is a session in Python where I can allocate a large, but fulfillable, number of

[issue19675] Pool dies with excessive workers, but does not cleanup

2013-11-20 Thread Ned Deily
Changes by Ned Deily n...@acm.org: -- keywords: +patch nosy: +sbt ___ Python tracker rep...@bugs.python.org http://bugs.python.org/issue19675 ___ ___ Python-bugs-list