Christopher Larson cf60f95d9f cooker: roll our own process pool ...

This fixes the hang issue encountered with parse errors. The underlying issue
seems to have been the pool.terminate(). This sends SIGTERM to each of the
multiprocessing pool's processes, however, a python process terminating in
this fashion can corrupt any queues it's interacting with, causing a number of
problems for us (e.g. the queue that sends events to the UI).

So instead of using multiprocessing's pool, we roll our own, with the ability
to cancel the work. In the very long term, the python concurrent.futures
module introduced in python 3.2 could be used to resolve this as well.

(Bitbake rev: 7c39cfd8e060cca8753ac4114775447b18e13067)

Signed-off-by: Christopher Larson <chris_larson@mentor.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

2012-02-22 20:25:29 +00:00

..

bb

cooker: roll our own process pool

2012-02-22 20:25:29 +00:00

ply

Add pysh, ply, and codegen to lib/ to prepare for future work

2010-08-03 14:06:07 +01:00

prserv

prserv: Do not ping PRService if not required

2012-02-01 15:08:42 +00:00

codegen.py

Add pysh, ply, and codegen to lib/ to prepare for future work

2010-08-03 14:06:07 +01:00

progressbar.py

Experimental usage of the 'progressbar' module

2011-01-04 14:46:42 +00:00