This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author glangford
Recipients Sebastian.Kreft.Deezer, bquinlan, glangford, mark.dickinson, pitrou, python-dev, sbt, tim.peters, vstinner
Date 2014-06-04.18:47:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <>
> the wait is actually returning after the 15 seconds, although nothing is reported as finished...What kind of debug information from the futures would be useful?

What is the state of the pending Futures that wait() is stuck on? (e.g. display f.running() and f.done() ). This could be logged any time the "done" set is empty after wait() returns. For each "stuck" Future, was it previously logged as completed by a prior call to wait()?

What is the state of the ProcessPoolExecutor that the futures have been submitted to? Does it still function? (e.g. try submitting a trivial Future to the executor).
Date User Action Args
2014-06-04 18:47:55glangfordsetrecipients: + glangford, tim.peters, bquinlan, mark.dickinson, pitrou, vstinner, python-dev, sbt, Sebastian.Kreft.Deezer
2014-06-04 18:47:55glangfordsetmessageid: <>
2014-06-04 18:47:55glangfordlinkissue20319 messages
2014-06-04 18:47:55glangfordcreate