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.
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>
logger.warn("runbuilds: schedule exception %s" % str(e))
def handle_noargs(self, **options):
+ self.runbuild()
+
signal.signal(signal.SIGUSR1, lambda sig, frame: None)
while True: