From: Mark Hatle <mark.hatle@windriver.com>
To: <bitbake-devel@lists.openembedded.org>
Subject: Re: [PATCH 2/8] knotty.py: Extend knotty to support "real time" log tail for tasks
Date: Mon, 17 Sep 2012 19:13:09 -0500 [thread overview]
Message-ID: <5057BC95.5070704@windriver.com> (raw)
In-Reply-To: <1347921818-60562-3-git-send-email-jason.wessel@windriver.com>
On 9/17/12 5:43 PM, Jason Wessel wrote:
> This patch provides the capability to knotty to have a higher log
> level where the individual tasks logs can be multiplexed to stdio.
> This is highly desirable for several different use cases.
>
> 1) You can visually spot "hot spots" in building parallel tasks
>
> 2) The relative order an sequence of events can be determined in
> difficult to diagnose inter-related library problems.
>
> 3) It provides a nice way to see what all is actually going on and
> getting logged by various tasks such as a kernel compile where you
> might want to actually look at the output in a build over build
> scenario.
>
> 4) There are most certainly other aspects where this is useful.
>
> The primary control is to set the BB_RT_LOGLEVEL = "2" in your
> local.conf. Additional capabilities will follow in successive
> patches. When parallel tasks are enabled, the logs will be
> multiplexed and prefixed with the PID of the task. In the
> non-parallel case there is no PID prefix as everything is linear.
>
> (LOCAL REV: NOT UPSTREAM)
As any FYI, this adds the new BB_RT_LOGLEVEL. If this patch is applied, then
BB_RT_LOGLEVEL should be added to BB_HASHCONFIG_WHITELIST in bitbake.conf.
--Mark
next prev parent reply other threads:[~2012-09-18 0:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-17 22:43 [PATCH 0/8] knotty: Interactive logging changes Jason Wessel
2012-09-17 22:43 ` [PATCH 1/8] bitbake: Unbuffer stdout for log files Jason Wessel
2012-09-18 0:46 ` Chris Larson
2012-09-18 1:15 ` Jason Wessel
2012-09-17 22:43 ` [PATCH 2/8] knotty.py: Extend knotty to support "real time" log tail for tasks Jason Wessel
2012-09-18 0:13 ` Mark Hatle [this message]
2012-09-17 22:43 ` [PATCH 3/8] knotty.py: Add the ability to dynamically select loglevel from stdin Jason Wessel
2012-09-17 22:43 ` [PATCH 4/8] msg.py, knotty.py: Allow dynamic toggle of the debug log level Jason Wessel
2012-09-17 22:43 ` [PATCH 5/8] knotty.py: update footer on dynamic log level change Jason Wessel
2012-09-17 22:43 ` [PATCH 6/8] knotty.py: Add interactive commands to knotty Jason Wessel
2012-09-17 22:43 ` [PATCH 7/8] knotty.py: Add ability to dynamically toggle log location Jason Wessel
2012-09-17 22:43 ` [PATCH 8/8] knotty.py: Handle rare interrupted select call Jason Wessel
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=5057BC95.5070704@windriver.com \
--to=mark.hatle@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.