public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Diego Novillo <dnovillo@google.com>
To: Andreas Schwab <schwab@redhat.com>
Cc: gcc@gnu.org, libstdc++@gcc.gnu.org
Subject: Re: Spurious libstdc++ testsuite failures because of truncated buffered output
Date: Fri, 18 Mar 2011 16:27:00 -0000	[thread overview]
Message-ID: <AANLkTin+NSN3xNzKuwk7gne-uvNiG2vPcSWwUq2uMHq3@mail.gmail.com> (raw)
In-Reply-To: <m37hbws9ry.fsf@redhat.com>

On Fri, Mar 18, 2011 at 11:55, Andreas Schwab <schwab@redhat.com> wrote:
> Diego Novillo <dnovillo@google.com> writes:
>
>> Is there a way to increase dejagnu's buffering?
>
> expect(1):
>
>       match_max [-d] [-i spawn_id] [size]
>             defines the size of the buffer  (in  bytes)  used  internally  by
>             expect.  With no size argument, the current size is returned.
>
>             With  the -d flag, the default size is set.  (The initial default
>             is 2000.)  With the -i flag, the size is set for the named  spawn
>             id, otherwise it is set for the current process.

Thanks, but I don't think match_max affects this.  It's the output
from the compiler that is being truncated.  I modified conformance.exp
with a match_max value 10x the limit I need, but the failures are
still there:

Index: testsuite/libstdc++-dg/conformance.exp
===================================================================
--- testsuite/libstdc++-dg/conformance.exp      (revision 171068)
+++ testsuite/libstdc++-dg/conformance.exp      (working copy)
@@ -21,6 +21,8 @@
 # Initialization.
 dg-init

+match_max -d 10000000
+
 # Build the support objects.
 v3-build_support

Running <bld>/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp ...
FAIL: decimal/mixed-mode_neg.cc  (test for errors, line 196)
FAIL: decimal/mixed-mode_neg.cc  (test for errors, line 197)
FAIL: decimal/mixed-mode_neg.cc  (test for errors, line 198)
FAIL: decimal/mixed-mode_neg.cc  (test for errors, line 199)
FAIL: decimal/mixed-mode_neg.cc  (test for errors, line 200)
FAIL: decimal/mixed-mode_neg.cc  (test for errors, line 201)
FAIL: decimal/mixed-mode_neg.cc  (test for errors, line 202)
FAIL: decimal/mixed-mode_neg.cc  (test for errors, line 203)

The output is clearly truncated, right before the first 'PASS' result, I see:

[ ... ]/x86_64-unknown-linux-gnu/libstdc++-v3/include/decimal/decimal.h:83:3:
note: std::decimal::decimal32&
std::decimal::decimal32::operator/=(long int)^M
/usr/local/google/hom      <<<< TRUNCATED
PASS: decimal/mixed-mode_neg.cc  (test for errors, line 43)
PASS: decimal/mixed-mode_neg.cc  (test for errors, line 44)


Diego.

  reply	other threads:[~2011-03-18 16:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-18 15:04 Diego Novillo
2011-03-18 15:30 ` Paolo Carlini
2011-03-18 15:36   ` Diego Novillo
2011-03-18 15:40     ` Paolo Carlini
2011-03-18 15:43       ` Diego Novillo
2011-03-18 16:01     ` Joseph S. Myers
2011-03-18 16:31       ` Diego Novillo
2011-03-18 15:56 ` Andreas Schwab
2011-03-18 16:27   ` Diego Novillo [this message]
2011-03-18 18:05     ` Andreas Schwab
2011-03-18 18:41       ` Diego Novillo

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=AANLkTin+NSN3xNzKuwk7gne-uvNiG2vPcSWwUq2uMHq3@mail.gmail.com \
    --to=dnovillo@google.com \
    --cc=gcc@gnu.org \
    --cc=libstdc++@gcc.gnu.org \
    --cc=schwab@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 read-only IMAP folder(s) and NNTP newsgroup(s).