[issue12364] Deadlock in test_concurrent_futures

2012-01-08 Thread Ross Lagerwall
Ross Lagerwall added the comment: Thanks! -- assignee: -> rosslagerwall resolution: -> fixed stage: -> committed/rejected status: open -> closed type: -> behavior ___ Python tracker ___

[issue12364] Deadlock in test_concurrent_futures

2012-01-07 Thread Roundup Robot
Roundup Robot added the comment: New changeset 26389e9efa9c by Ross Lagerwall in branch '3.2': Issue #12364: Fix a hang in concurrent.futures.ProcessPoolExecutor. http://hg.python.org/cpython/rev/26389e9efa9c New changeset 25f879011102 by Ross Lagerwall in branch 'default': Merge with 3.2 for #

[issue12364] Deadlock in test_concurrent_futures

2012-01-03 Thread Antoine Pitrou
Antoine Pitrou added the comment: Well I was sure I had added this code for a reason, but the tests seem to run without... Just a comment: the test isn't ProcessPoolExecutor-specific, so it should really be in the generic tests. -- ___ Python track

[issue12364] Deadlock in test_concurrent_futures

2012-01-02 Thread Ross Lagerwall
Changes by Ross Lagerwall : Added file: http://bugs.python.org/file24129/itest.py ___ Python tracker ___ ___ Python-bugs-list mailing list Uns

[issue12364] Deadlock in test_concurrent_futures

2012-01-02 Thread Ross Lagerwall
Ross Lagerwall added the comment: Retrieving the result of a future after the executor has been shut down can cause a hang. It seems like this regression was introduced in a76257a99636. This regression exists only for ProcessPoolExecutor. The problem is that even if there are pending work it

[issue12364] Deadlock in test_concurrent_futures

2011-07-05 Thread STINNER Victor
Changes by STINNER Victor : -- title: Timeout (1 hour) in test_concurrent_futures.tearDown() on sparc solaris10 gcc 3.x -> Deadlock in test_concurrent_futures ___ Python tracker ___