From: Paolo Carlini <paolo.carlini@oracle.com>
To: Diego Novillo <dnovillo@google.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:40:00 -0000 [thread overview]
Message-ID: <4D837CE3.8020605@oracle.com> (raw)
In-Reply-To: <AANLkTi=P5RjUFmOPv6E_knj5sog96kR9NNYsVps3oZcg@mail.gmail.com>
On 03/18/2011 04:35 PM, Diego Novillo wrote:
> 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.
For sure if it's the *overall* number of bytes that matters, working
around the issue is simple, because the testcase can be trivially split
to 14 separate tests, one for each operation.
Paolo.
next prev parent reply other threads:[~2011-03-18 15:40 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 [this message]
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=4D837CE3.8020605@oracle.com \
--to=paolo.carlini@oracle.com \
--cc=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).