From: Ed Bartosh Date: Fri, 16 Sep 2016 16:22:35 +0000 (+0100) Subject: toaster: unlock BuildEnvirnoment when build is done X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=faa88272d656640c039572c5c8f3e6c56535b6f7;p=thirdparty%2Fopenembedded%2Fopenembedded-core-contrib.git 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. Signed-off-by: Ed Bartosh Signed-off-by: Michael Wood Signed-off-by: Richard Purdie --- diff --git a/lib/bb/ui/buildinfohelper.py b/lib/bb/ui/buildinfohelper.py index c93ee94d2c4..22469607d6a 100644 --- a/lib/bb/ui/buildinfohelper.py +++ b/lib/bb/ui/buildinfohelper.py @@ -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):