From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from 93-97-173-237.zone5.bethere.co.uk ([93.97.173.237] helo=tim.rpsys.net) by linuxtogo.org with esmtp (Exim 4.72) (envelope-from ) id 1S0hdP-000673-IB for bitbake-devel@lists.openembedded.org; Thu, 23 Feb 2012 23:59:35 +0100 Received: from localhost (localhost [127.0.0.1]) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id q1NMpCp8030145; Thu, 23 Feb 2012 22:51:12 GMT Received: from tim.rpsys.net ([127.0.0.1]) by localhost (tim.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 26703-07; Thu, 23 Feb 2012 22:51:09 +0000 (GMT) Received: from [192.168.3.10] ([192.168.3.10]) (authenticated bits=0) by tim.rpsys.net (8.13.6/8.13.8) with ESMTP id q1NMp3BM030137 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 23 Feb 2012 22:51:04 GMT Message-ID: <1330037463.22167.5.camel@ted> From: Richard Purdie To: Dongxiao Xu Date: Thu, 23 Feb 2012 22:51:03 +0000 In-Reply-To: References: X-Mailer: Evolution 3.2.2- Mime-Version: 1.0 X-Virus-Scanned: amavisd-new at rpsys.net Cc: bitbake-devel@lists.openembedded.org Subject: Re: [PATCH 9/9] runqueue: fire sceneQueueTaskStarted event when a setscene queue starts X-BeenThere: bitbake-devel@lists.openembedded.org X-Mailman-Version: 2.1.11 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Feb 2012 22:59:35 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Thu, 2012-02-23 at 21:47 +0800, Dongxiao Xu wrote: > The current code prints a log when a setscene task starts, therefore > the progressbar in hob will not receive it. Use a sceneQueueTaskStarted > event instead. > > Signed-off-by: Shane Wang > Signed-off-by: Dongxiao Xu > --- > lib/bb/runqueue.py | 10 ++++++++++ > 1 files changed, 10 insertions(+), 0 deletions(-) > > diff --git a/lib/bb/runqueue.py b/lib/bb/runqueue.py > index d1d9ad9..ef28415 100644 > --- a/lib/bb/runqueue.py > +++ b/lib/bb/runqueue.py > @@ -1653,6 +1653,9 @@ class RunQueueExecuteScenequeue(RunQueueExecute): > self.task_skip(task) > return True > > + startevent = sceneQueueTaskStarted(task, self.stats, self.rq) > + bb.event.fire(startevent, self.cfgData) > + > pid, pipein, pipeout = self.fork_off_task(fn, realtask, taskname) > > self.build_pids[pid] = task > @@ -1720,6 +1723,13 @@ class runQueueTaskStarted(runQueueEvent): > runQueueEvent.__init__(self, task, stats, rq) > self.noexec = noexec > > +class sceneQueueTaskStarted(runQueueTaskStarted): > + """ > + Event notifing a setscene task was started > + """ > + def __init__(self, task, stats, rq, noexec=False): > + runQueueTaskStarted.__init__(self, task, stats, rq, noexec) > + This one has me a little worried since it inherits runQueueTaskStarted and a UI might confuse this with real runQueueTaskStarted() events. Is there something else we can inherit here? Cheers, Richard