From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Xu, Dongxiao" <dongxiao.xu@intel.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 9/9] runqueue: fire sceneQueueTaskStarted event when a setscene queue starts
Date: Fri, 24 Feb 2012 00:51:08 +0000 [thread overview]
Message-ID: <1330044668.25226.19.camel@ted> (raw)
In-Reply-To: <1330043649.8145.59.camel@dongxiao-osel>
On Fri, 2012-02-24 at 08:34 +0800, Xu, Dongxiao wrote:
> On Thu, 2012-02-23 at 22:51 +0000, Richard Purdie wrote:
> > 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 <shane.wang@intel.com>
> > > Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com>
> > > ---
> > > 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?
>
> Hi Richard,
>
> Here we inherit runQueueTaskStarted event is because we saw the
> sceneQueueTaskFailed event inherits runQueueTaskFailed in existing code.
>
> What about change both of sceneQueueTaskxxx directly inherit
> runQueueEvent?
That sounds reasonable to me. sceneQueueTaskFailed sounds like a bug and
might explain an error I keep seeing in knotty but haven't looked
into/reported yet! You might fix a bug by changing that :)
Cheers,
Richard
next prev parent reply other threads:[~2012-02-24 0:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 13:47 [PATCH 0/9][PULL] Hob2: bitbake related changes Dongxiao Xu
2012-02-23 13:47 ` [PATCH 1/9] cache: Use configuration's hash value to validate cache Dongxiao Xu
2012-02-23 13:47 ` [PATCH 2/9] command.py: add resolve option for generateTargetsTree API Dongxiao Xu
2012-02-23 13:47 ` [PATCH 3/9] event.py: Add new events RequestPackageInfo and PackageInfo Dongxiao Xu
2012-02-23 13:47 ` [PATCH 4/9] bitbake: change for adding progress bar in Hob2 Dongxiao Xu
2012-02-23 13:47 ` [PATCH 5/9] bitbake: add -B option to bind with interface Dongxiao Xu
2012-02-23 13:47 ` [PATCH 6/9] bitbake: Add client socket info for BitBakeServerConnection Dongxiao Xu
2012-02-23 13:47 ` [PATCH 7/9] command.py: add new API to get the cpu count on the server Dongxiao Xu
2012-02-23 13:47 ` [PATCH 8/9] command.py: Add a new API triggerEvent() Dongxiao Xu
2012-02-23 13:47 ` [PATCH 9/9] runqueue: fire sceneQueueTaskStarted event when a setscene queue starts Dongxiao Xu
2012-02-23 22:51 ` Richard Purdie
2012-02-24 0:34 ` Xu, Dongxiao
2012-02-24 0:51 ` Richard Purdie [this message]
2012-02-23 22:55 ` [PATCH 0/9][PULL] Hob2: bitbake related changes Richard Purdie
-- strict thread matches above, loose matches on Subject: below --
2012-01-13 8:30 [PATCH 0/9 v3][PULL] Hob: " Dongxiao Xu
2012-01-13 8:30 ` [PATCH 9/9] runqueue: fire sceneQueueTaskStarted event when a setscene queue starts Dongxiao Xu
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=1330044668.25226.19.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=dongxiao.xu@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox