All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: toaster@yoctoproject.org
Subject: [PATCH 3/7] runbuilds: process builds on SIGUSR1
Date: Tue, 13 Sep 2016 16:21:00 +0300	[thread overview]
Message-ID: <316490761498eec80351ff72c9bd4404f6d52db4.1473769704.git.ed.bartosh@linux.intel.com> (raw)
In-Reply-To: <cover.1473769704.git.ed.bartosh@linux.intel.com>
In-Reply-To: <cover.1473769704.git.ed.bartosh@linux.intel.com>

Run main processing function 'runbuild' only if SIGUSR1 is
received. This signal is sent by Toaster when build status
is changed (either started, cancelled or finished).

This should stop continuous database polling as run_builds function
will be called only when needed, i.e. after build status is changed.

[YOCTO #8918]

Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com>
---
 bitbake/lib/toaster/bldcontrol/management/commands/runbuilds.py | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/bitbake/lib/toaster/bldcontrol/management/commands/runbuilds.py b/bitbake/lib/toaster/bldcontrol/management/commands/runbuilds.py
index a703770..61a520c 100644
--- a/bitbake/lib/toaster/bldcontrol/management/commands/runbuilds.py
+++ b/bitbake/lib/toaster/bldcontrol/management/commands/runbuilds.py
@@ -11,9 +11,9 @@ from orm.models import Build, ToasterSetting, LogMessage, Target
 
 import os
 import logging
-import time
 import sys
 import traceback
+import signal
 
 logger = logging.getLogger("toaster")
 
@@ -175,6 +175,8 @@ class Command(NoArgsCommand):
             logger.warn("runbuilds: schedule exception %s" % str(e))
 
     def handle_noargs(self, **options):
+        signal.signal(signal.SIGUSR1, lambda sig, frame: None)
+
         while True:
+            signal.pause()
             self.runbuild()
-            time.sleep(1)
-- 
2.1.4



  parent reply	other threads:[~2016-09-13 13:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-13 13:20 [PATCH 0/7] Fix for #8918: Change the way we handle queued builds Ed Bartosh
2016-09-13 13:20 ` [PATCH 1/7] toaster: implement signal_runbuilds function Ed Bartosh
2016-09-13 13:20 ` [PATCH 2/7] toaster: notify runbuilds when build status changes Ed Bartosh
2016-09-13 13:21 ` Ed Bartosh [this message]
2016-09-13 13:21 ` [PATCH 4/7] runbuilds: process builds on start Ed Bartosh
2016-09-13 13:21 ` [PATCH 5/7] runbuilds: code cleanup - whitespaces, long lines Ed Bartosh
2016-09-13 13:21 ` [PATCH 6/7] runbuilds: code cleanup - remove unused imports Ed Bartosh
2016-09-13 13:21 ` [PATCH 7/7] toaster: unlock BuildEnvirnoment when build is done Ed Bartosh
2016-09-16 16:25   ` Michael Wood

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=316490761498eec80351ff72c9bd4404f6d52db4.1473769704.git.ed.bartosh@linux.intel.com \
    --to=ed.bartosh@linux.intel.com \
    --cc=toaster@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.