From: Diego Novillo <dnovillo@google.com>
To: Paolo Carlini <paolo.carlini@oracle.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 15:36:00 -0000 [thread overview]
Message-ID: <AANLkTi=P5RjUFmOPv6E_knj5sog96kR9NNYsVps3oZcg@mail.gmail.com> (raw)
In-Reply-To: <4D837A7B.8020005@oracle.com>
On Fri, Mar 18, 2011 at 11:30, Paolo Carlini <paolo.carlini@oracle.com> wrote:
> Hi
>>
>> 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.
>
> Honestly, I know very little about the dejagnu buffering, but I'm having a
> quick look to the issue and I'm rather surprised that you are seeing it for
> these particular errors and nowhere else in the testsuite: here, on the
> libstdc++.log of x86_64-linux, I see just 9 candidates listed, and I'm
> pretty sure that in terms of error messages we have much, much, longer
> examples, when templates are involved in particular. What I'm missing?
I don't really know why the others don't fail, but I will take a look.
In this particular case, the output is truncated after 1,032,134
bytes are printed. So I can only speculate that no other tests
generate more than this number of bytes in output. I'll take a look.
Diego.
next prev parent reply other threads:[~2011-03-18 15:36 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 [this message]
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='AANLkTi=P5RjUFmOPv6E_knj5sog96kR9NNYsVps3oZcg@mail.gmail.com' \
--to=dnovillo@google.com \
--cc=gcc@gnu.org \
--cc=libstdc++@gcc.gnu.org \
--cc=paolo.carlini@oracle.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).