All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Seebach <peter.seebach@windriver.com>
To: <bitbake-devel@lists.openembedded.org>
Subject: [PATCH 0/3] Variable tracking: Cleaned up and less buggy
Date: Thu, 9 Aug 2012 15:23:15 -0500	[thread overview]
Message-ID: <cover.1344543257.git.peter.seebach@windriver.com> (raw)

So, I finally got around to looking at a couple of "hmm, that looks
funny" thoughts I had about the variable tracking, and went and cleaned
things up. Appends were being reported twice in many cases, but also
they were reporting ever-increasing stuff for large values; in my
build tree, the output for BBCLASSEXTEND *alone* was 10MB. (!!)

So to summarize:

-rw-r--r-- 1 seebs seebs 11078986 2012-08-09 13:09 bitbake-e.prepatch
-rw-r--r-- 1 seebs seebs   635832 2012-08-09 15:02 bitbake-e.postpatch

Of these files, the second contains more actual information about how
variables got set.

I've left the old patch alone and done this as a new patch. I could
merge them, but I figure anyone who's been using the old patch would
like to have a patch that can be applied on top of it. :)

The following changes since commit 23bd5300b4a99218a15f4f6b0ab4091d63a602a5:
  Richard Purdie (1):
        data_smart: Fix unanchored regexp causing strange parsing issue

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib seebs/ntracking
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/ntracking

Peter Seebach (3):
  data_smart.py: Provide (optional) logging of variable modifications
  data_smart.py: Track configuration file inclusions
  data_smart.py: Fix variable tracking

 lib/bb/cooker.py                     |    2 +
 lib/bb/data.py                       |   65 ++++++++++---
 lib/bb/data_smart.py                 |  177 +++++++++++++++++++++++++++-------
 lib/bb/parse/__init__.py             |    6 +-
 lib/bb/parse/ast.py                  |   70 ++++++++------
 lib/bb/parse/parse_py/ConfHandler.py |    4 +-
 6 files changed, 243 insertions(+), 81 deletions(-)




             reply	other threads:[~2012-08-09 20:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-09 20:23 Peter Seebach [this message]
2012-08-09 20:23 ` [PATCH 1/3] data_smart.py: Provide (optional) logging of variable modifications Peter Seebach
2012-08-09 20:23 ` [PATCH 2/3] data_smart.py: Track configuration file inclusions Peter Seebach
2012-08-09 20:23 ` [PATCH 3/3] data_smart.py: Fix variable tracking Peter Seebach

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=cover.1344543257.git.peter.seebach@windriver.com \
    --to=peter.seebach@windriver.com \
    --cc=bitbake-devel@lists.openembedded.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.