From: Patrick Ohly <patrick.ohly@intel.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: bitbake-devel <bitbake-devel@lists.openembedded.org>
Subject: Re: [PATCH] cooker: Fix incorrect dot file generation
Date: Wed, 20 Jul 2016 17:34:24 +0200 [thread overview]
Message-ID: <1469028864.20940.0.camel@intel.com> (raw)
In-Reply-To: <1469027297.23580.17.camel@linuxfoundation.org>
On Wed, 2016-07-20 at 16:08 +0100, Richard Purdie wrote:
> In the runqueue cleanup/conversion, "dep" was mistakenly used where "tid" should
> be leading to incorrect task-depends.dot files and causing general confusion.
> Fix this, its clearly incorrect looking at the code.
>
> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
>
> diff --git a/bitbake/lib/bb/cooker.py b/bitbake/lib/bb/cooker.py
> index 9bd3460..a73a55d 100644
> --- a/bitbake/lib/bb/cooker.py
> +++ b/bitbake/lib/bb/cooker.py
> @@ -744,7 +744,7 @@ class BBCooker:
> for dep in rq.rqdata.runtaskentries[tid].depends:
> depfn = bb.runqueue.fn_from_tid(dep)
> deppn = self.recipecache.pkg_fn[depfn]
> - dotname = "%s.%s" % (pn, bb.runqueue.taskname_from_tid(dep))
> + dotname = "%s.%s" % (pn, bb.runqueue.taskname_from_tid(tid))
> if not dotname in depend_tree["tdepends"]:
> depend_tree["tdepends"][dotname] = []
> depend_tree["tdepends"][dotname].append("%s.%s" % (deppn, bb.runqueue.taskname_from_tid(dep)))
+1, this is indeed fixing the issue I was seeing. Thanks!
--
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.
prev parent reply other threads:[~2016-07-20 15:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 15:08 [PATCH] cooker: Fix incorrect dot file generation Richard Purdie
2016-07-20 15:34 ` Patrick Ohly [this message]
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=1469028864.20940.0.camel@intel.com \
--to=patrick.ohly@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 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.