From: Jason Wessel <jason.wessel@windriver.com>
To: Chris Larson <clarson@kergoth.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 1/8] bitbake: Unbuffer stdout for log files
Date: Mon, 17 Sep 2012 20:15:22 -0500 [thread overview]
Message-ID: <5057CB2A.9030508@windriver.com> (raw)
In-Reply-To: <CABcZANkRiYXarfHjqF9u2tuqyqJZtqDuom3Ueta4AwYxENP_Sg@mail.gmail.com>
On 09/17/2012 07:46 PM, Chris Larson wrote:
> On Mon, Sep 17, 2012 at 3:43 PM, Jason Wessel
> <jason.wessel@windriver.com> wrote:
>> It is possible to lose critical log data when python exits in an
>> unorderly fashion via segmentation fault or certain types of crashes.
>> This is because the buffer characteristics are inherited from the top
>> level stdout, which should be set to unbuffered, for the purpose of
>> all the forked children.
>>
>> This pushes the buffering to the OS, instead of having python managing
>> the buffers in its stream handler class.
>>
>> This change is also to provide the ability to tail logs written from
>> processes in "real time" because they would be written in an orderly
>> fashion depending upon the OS characteristics for the file I/O.
>>
>> (LOCAL REV ONLY: NOT UPSTREAM)
>>
>> Signed-off-by: Jason Wessel <jason.wessel@windriver.com>
>
> I'm assuming you forgot to rebase -i and remove the LOCAL REV ONLY? :)
Oops :-)
I can resend the patches, but I did re-base against the head but for some reason the filter was not working.
Jason.
next prev parent reply other threads:[~2012-09-18 1:28 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 [this message]
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
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=5057CB2A.9030508@windriver.com \
--to=jason.wessel@windriver.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=clarson@kergoth.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox