]> git.ipfire.org Git - thirdparty/openembedded/openembedded-core-contrib.git/commit
bitbake: toaster: unlock BuildEnvirnoment when build is done
authorEd Bartosh <ed.bartosh@linux.intel.com>
Fri, 16 Sep 2016 16:22:35 +0000 (17:22 +0100)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Wed, 21 Sep 2016 20:58:06 +0000 (21:58 +0100)
commit7a3cccbd1aa4333df6ab46d87b4b1f39d1fe683d
treecf680b6503158c7372759614c981e61401170541
parentad04a6324e8fd6c6de87bad6a366d7077835947c
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>
bitbake/lib/bb/ui/buildinfohelper.py