From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Ed Bartosh <ed.bartosh@linux.intel.com>,
bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH] cooker: check if target contains task
Date: Thu, 15 Sep 2016 09:03:24 +0100 [thread overview]
Message-ID: <1473926604.7207.71.camel@linuxfoundation.org> (raw)
In-Reply-To: <1473432540-22120-1-git-send-email-ed.bartosh@linux.intel.com>
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
Cheers,
Richard
next prev parent reply other threads:[~2016-09-15 8:03 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 [this message]
2016-09-15 8:22 ` Ed Bartosh
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=1473926604.7207.71.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=ed.bartosh@linux.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 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.