From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Cc: thuth@redhat.com
Subject: Re: [Qemu-devel] [PATCH] tap: flush STDOUT on newline
Date: Tue, 15 Jan 2019 19:59:36 +0100 [thread overview]
Message-ID: <f3a03f92-a71b-2032-2a81-715d222d0cf5@redhat.com> (raw)
In-Reply-To: <1547574976-6372-1-git-send-email-pbonzini@redhat.com>
On 1/15/19 6:56 PM, Paolo Bonzini wrote:
> This makes it easier to follow what is going on.
>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>
> ---
> scripts/tap-driver.pl | 1 +
> scripts/tap-merge.pl | 1 +
> 2 files changed, 2 insertions(+)
>
> diff --git a/scripts/tap-driver.pl b/scripts/tap-driver.pl
> index 5e59b5d..6621a5c 100755
> --- a/scripts/tap-driver.pl
> +++ b/scripts/tap-driver.pl
> @@ -313,6 +313,7 @@ sub main ()
> my $iterator = TAP::Parser::Iterator::Stream->new(\*STDIN);
> my $parser = TAP::Parser->new ({iterator => $iterator });
>
> + STDOUT->autoflush(1);
> while (defined (my $cur = $parser->next))
> {
> # Parsing of TAP input should stop after a "Bail out!" directive.
> diff --git a/scripts/tap-merge.pl b/scripts/tap-merge.pl
> index 59e3fa5..10ccf57 100755
> --- a/scripts/tap-merge.pl
> +++ b/scripts/tap-merge.pl
> @@ -53,6 +53,7 @@ sub main ()
> my $testno = 0; # Number of test results seen so far.
> my $bailed_out = 0; # Whether a "Bail out!" directive has been seen.
>
> + STDOUT->autoflush(1);
> while (defined (my $cur = $parser->next))
> {
> if ($cur->is_bailout)
>
next prev parent reply other threads:[~2019-01-15 18:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 17:56 [Qemu-devel] [PATCH] tap: flush STDOUT on newline Paolo Bonzini
2019-01-15 18:03 ` Eric Blake
2019-01-15 18:59 ` Philippe Mathieu-Daudé [this message]
2019-01-21 5:12 ` no-reply
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=f3a03f92-a71b-2032-2a81-715d222d0cf5@redhat.com \
--to=philmd@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.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;
as well as URLs for NNTP newsgroup(s).