bitbake: prserv/serv: Ensure sync happens in the correct thread
authorRichard Purdie <richard.purdie@linuxfoundation.org>
Tue, 4 Nov 2014 14:02:32 +0000 (14:02 +0000)
committerPatrick Ohly <patrick.ohly@intel.com>
Fri, 9 Jan 2015 16:52:21 +0000 (08:52 -0800)
commitf082bca6572d6a71b2d53b7634bc770f2b4b2b56
treed47abb46a5ca6f83d798af98cc1cd6a7646d283a
parentf4ea13eccbb387bdd4b073558b49e936de4f0660
bitbake: prserv/serv: Ensure sync happens in the correct thread

The sync/commit calls are happening in the submission thread which can
race against the handler. The handler may start new transactions which
then causes the submission thread to error with "cannot start a
transaction within a transaction".

The fix is to move the calls to the correct thread.

(Bitbake rev: 08cf468ab751f4c6e4ffdab2d8e5d748f7698593)

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Patrick Ohly <patrick.ohly@intel.com>
bitbake/lib/prserv/serv.py