[issue21899] Futures are not marked as completed

2014-07-16 Thread Sebastian Kreft
Sebastian Kreft added the comment: After more testing I finally found that in fact the process is not being killed. That means that there is no problem with the futures. But instead it is probably related with subprocess deadlocking, as the problematic process does not consume any CPU. Sorry

[issue21899] Futures are not marked as completed

2014-07-01 Thread Ned Deily
Changes by Ned Deily : -- nosy: +bquinlan ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.o

[issue21899] Futures are not marked as completed

2014-07-01 Thread Sebastian Kreft
New submission from Sebastian Kreft: With Python 3.4.1 compiled from source, I'm having an issue in which every now and then some Futures are not marked as completed even though the underlying workload is done. My workload is launching two subprocess in parallel, and whenever one is ready, la