From: Ed Bartosh <ed.bartosh@linux.intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH] cooker: check if target contains task
Date: Thu, 15 Sep 2016 11:22:15 +0300 [thread overview]
Message-ID: <20160915082215.GA11487@linux.intel.com> (raw)
In-Reply-To: <1473926604.7207.71.camel@linuxfoundation.org>
On Thu, Sep 15, 2016 at 09:03:24AM +0100, Richard Purdie wrote:
> On Fri, 2016-09-09 at 17:49 +0300, Ed Bartosh wrote:
> > Task name was incorrectly added to the targets that already
> > contained :task suffix and fired with BuildInit event. This
> > caused Toaster to create incorrect Target objects and show
> > them in UI.
> >
> > [YOCTO #10221]
> >
> > Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com>
> > ---
> > bitbake/lib/bb/cooker.py | 3 ++-
> > 1 file changed, 2 insertions(+), 1 deletion(-)
> >
> > diff --git a/bitbake/lib/bb/cooker.py b/bitbake/lib/bb/cooker.py
> > index b7d7a7e..2952f9e 100644
> > --- a/bitbake/lib/bb/cooker.py
> > +++ b/bitbake/lib/bb/cooker.py
> > @@ -1421,7 +1421,8 @@ class BBCooker:
> > if not task.startswith("do_"):
> > task = "do_%s" % task
> >
> > - packages = ["%s:%s" % (target, task) for target in targets]
> > + packages = [target if ':' in target else '%s:%s' (target,
> > task) for target in targets]
> > +
> > bb.event.fire(bb.event.BuildInit(packages),
> > self.expanded_data)
> >
> > taskdata, runlist = self.buildTaskData(targets, task,
> > self.configuration.abort)
>
> I put this into a build without looking too closely, the result was
> near enough everything failed with failures like:
>
> http://autobuilder.yocto.io:8010/builders/buildtools/builds/37
>
Sorry for the typo. I'll send an update in a minute.
--
Regards,
Ed
next prev parent reply other threads:[~2016-09-15 8:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-09 14:49 [PATCH] cooker: check if target contains task Ed Bartosh
2016-09-15 8:03 ` Richard Purdie
2016-09-15 8:22 ` Ed Bartosh [this message]
2016-09-15 8:26 ` [PATCH v2] " Ed Bartosh
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=20160915082215.GA11487@linux.intel.com \
--to=ed.bartosh@linux.intel.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox