From: Diego Novillo <dnovillo@google.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: gcc@gnu.org, libstdc++@gcc.gnu.org
Subject: Re: Spurious libstdc++ testsuite failures because of truncated buffered output
Date: Fri, 18 Mar 2011 18:41:00 -0000 [thread overview]
Message-ID: <AANLkTikUao2YE3aiNrGnNUOfojxt_jgFdZ0FE8jrDKLE@mail.gmail.com> (raw)
In-Reply-To: <m2r5a45moc.fsf@igel.home>
On Fri, Mar 18, 2011 at 14:05, Andreas Schwab <schwab@linux-m68k.org> wrote:
> Diego Novillo <dnovillo@google.com> writes:
>
>> Thanks, but I don't think match_max affects this. It's the output
>> from the compiler that is being truncated.
>
> I don't see that problem on powerpc-linux (and I couldn't find any such
> failure on gcc-testresults).
It only happens in our builds that have very deep directory trees.
The extra long path names contribute to filling up whatever buffer
that dejagnu uses for output. I believe that if you manage to build
inside a tree this long, you'll be able to reproduce the problem:
$ pwd -P | wc -c
236
Diego.
prev parent reply other threads:[~2011-03-18 18:41 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
2011-03-18 18:05 ` Andreas Schwab
2011-03-18 18:41 ` Diego Novillo [this message]
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=AANLkTikUao2YE3aiNrGnNUOfojxt_jgFdZ0FE8jrDKLE@mail.gmail.com \
--to=dnovillo@google.com \
--cc=gcc@gnu.org \
--cc=libstdc++@gcc.gnu.org \
--cc=schwab@linux-m68k.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).