sysmo-bts
/
generic-poky
9
0
Fork 0
Code Pull Requests Releases Activity

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>
This commit is contained in:
Ed Bartosh 2016-09-16 17:22:35 +01:00 committed by Richard Purdie
parent ad04a6324e
commit 7a3cccbd1a
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
bitbake/lib/bb/ui/buildinfohelper.py
View File

@ -1524,9 +1524,7 @@ class BuildInfoHelper(object):
return
br_id, be_id = self.brbe.split(":")
be = BuildEnvironment.objects.get(pk = be_id)
be.lock = BuildEnvironment.LOCK_LOCK
be.save()
br = BuildRequest.objects.get(pk = br_id)
# if we're 'done' because we got cancelled update the build outcome
@ -1543,6 +1541,10 @@ class BuildInfoHelper(object):
else:
br.state = BuildRequest.REQ_FAILED
br.save()
be = BuildEnvironment.objects.get(pk = be_id)
be.lock = BuildEnvironment.LOCK_FREE
be.save()
signal_runbuilds()
def store_log_error(self, text):