Ed Bartosh 7a3cccbd1a bitbake: toaster: unlock BuildEnvirnoment when build is done ...

There is no need to lock build environment before changing
build status as this operation is very fast. However, there
is a need to unlock it after changing build status.

Explicitly unlocked BuildEnvironment after build reaches
final status SUCCEEDED, FAILED or CANCELLED. This should
allow runbuilds process to pickup next build faster.

(Bitbake rev: faa88272d656640c039572c5c8f3e6c56535b6f7)

Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com>
Signed-off-by: Michael Wood <michael.g.wood@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

2016-09-21 21:58:06 +01:00

..

bb

bitbake: toaster: unlock BuildEnvirnoment when build is done

2016-09-21 21:58:06 +01:00

bblayers

bitbake: bitbake: Initial multi-config support

2016-08-18 10:06:27 +01:00

bs4

bitbake: bitbake/bs4: Upgrade 4.3.2 -> 4.4.1 (python 3 version)

2016-06-02 08:24:02 +01:00

ply

bitbake: bitbake: Convert to python 3

2016-06-02 08:24:02 +01:00

progressbar

bitbake: lib: implement basic task progress support

2016-07-08 09:57:26 +01:00

prserv

bitbake: bitbake: Convert to python 3

2016-06-02 08:24:02 +01:00

toaster

bitbake: runbuilds: code cleanup - remove unused imports

2016-09-21 21:58:06 +01:00

codegen.py

bitbake: bitbake: Convert to python 3

2016-06-02 08:24:02 +01:00

pyinotify.py

bitbake: bitbake/pyinotify.py: Upgrade to py3 version

2016-06-02 08:24:02 +01:00