This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Spurious libstdc++ testsuite failures because of truncated buffered output

From: Paolo Carlini <paolo dot carlini at oracle dot com>
To: Diego Novillo <dnovillo at google dot com>
Cc: gcc at gnu dot org, libstdc++ at gcc dot gnu dot org
Date: Fri, 18 Mar 2011 16:40:19 +0100
Subject: Re: Spurious libstdc++ testsuite failures because of truncated buffered output
References: <AANLkTim+0aYi-eYTa6S0HSmyd6HeK_MJ65ALiKsdQtkx@mail.gmail.com> <4D837A7B.8020005@oracle.com> <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.

Follow-Ups:
- Re: Spurious libstdc++ testsuite failures because of truncated buffered output
  - From: Diego Novillo

References:
- Spurious libstdc++ testsuite failures because of truncated buffered output
  - From: Diego Novillo
- Re: Spurious libstdc++ testsuite failures because of truncated buffered output
  - From: Paolo Carlini
- Re: Spurious libstdc++ testsuite failures because of truncated buffered output
  - From: Diego Novillo

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]