summaryrefslogtreecommitdiffstats
path: root/bitbake/lib/toaster/bldcontrol
diff options
context:
space:
mode:
authorEd Bartosh <ed.bartosh@linux.intel.com>2016-09-16 17:22:32 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-09-21 21:58:06 +0100
commit323b81a08380c9660524b21a65d27c225d02c953 (patch)
tree722956d3bd57284f2677f1212fc5864975c53a3d /bitbake/lib/toaster/bldcontrol
parent64d284b26c2e9b0fcd03119302bd8512fe317cc1 (diff)
downloadpoky-323b81a08380c9660524b21a65d27c225d02c953.tar.gz
bitbake: runbuilds: process builds on start
If Toaster is stopped incorrectly there could be some build requests and builds in incorrect state left from the previous run. Running main processing function on start should take care of those. (Bitbake rev: 6b9f8f6bb51d1aa2ca4effc34e076e331d0cb8d1) 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>
Diffstat (limited to 'bitbake/lib/toaster/bldcontrol')
-rw-r--r--bitbake/lib/toaster/bldcontrol/management/commands/runbuilds.py2
1 files changed, 2 insertions, 0 deletions
diff --git a/bitbake/lib/toaster/bldcontrol/management/commands/runbuilds.py b/bitbake/lib/toaster/bldcontrol/management/commands/runbuilds.py
index 61a520c6ce..7df81dc5d1 100644
--- a/bitbake/lib/toaster/bldcontrol/management/commands/runbuilds.py
+++ b/bitbake/lib/toaster/bldcontrol/management/commands/runbuilds.py
@@ -175,6 +175,8 @@ class Command(NoArgsCommand):
175 logger.warn("runbuilds: schedule exception %s" % str(e)) 175 logger.warn("runbuilds: schedule exception %s" % str(e))
176 176
177 def handle_noargs(self, **options): 177 def handle_noargs(self, **options):
178 self.runbuild()
179
178 signal.signal(signal.SIGUSR1, lambda sig, frame: None) 180 signal.signal(signal.SIGUSR1, lambda sig, frame: None)
179 181
180 while True: 182 while True: