public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Diego Novillo <dnovillo@google.com>
To: gcc@gnu.org, libstdc++@gcc.gnu.org
Subject: Spurious libstdc++ testsuite failures because of truncated buffered output
Date: Fri, 18 Mar 2011 15:04:00 -0000	[thread overview]
Message-ID: <AANLkTim+0aYi-eYTa6S0HSmyd6HeK_MJ65ALiKsdQtkx@mail.gmail.com> (raw)

I am getting several failures in decimal/mixed-mode_neg.cc:

FAIL: decimal/mixed-mode_neg.cc  (test for errors, line 195)
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)

This test expects syntax errors in all these lines, and the compiler
is indeed flagging them but the output from the compiler is so big
that dejagnu truncates it.  The testsuite never sees the error
messages starting at line 195 (I can see the output truncated in
libstdc++.log).

Is there a way to increase dejagnu's buffering?  This does not happen,
if I simply run the build in a shallower build tree, but that is not a
viable alternative.

Any suggestions on how to address this, short of butchering this test?


Thanks.  Diego.

             reply	other threads:[~2011-03-18 15:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-18 15:04 Diego Novillo [this message]
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
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=AANLkTim+0aYi-eYTa6S0HSmyd6HeK_MJ65ALiKsdQtkx@mail.gmail.com \
    --to=dnovillo@google.com \
    --cc=gcc@gnu.org \
    --cc=libstdc++@gcc.gnu.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 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).