public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dank at kegel dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/12096] New: dejagnu truncates output from spawned commands randomly, causing intermittant failed tests
Date: Thu, 28 Aug 2003 17:33:00 -0000	[thread overview]
Message-ID: <20030828173345.12096.dank@kegel.com> (raw)

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12096

           Summary: dejagnu truncates output from spawned commands randomly,
                    causing intermittant failed tests
           Product: gcc
           Version: 3.3.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: other
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: dank at kegel dot com
                CC: gcc-bugs at gcc dot gnu dot org

This is most likely a bug in expect, not in any part of gcc,
but it deserves mention here nonetheless. 
Tests which tend to be affected by this are those that generate
lots of output.  I've observed it cause the following most often:

FAIL: gcc.dg/cpp/tr-warn3.c 
FAIL: gcc.dg/format/c90-printf-1.c 
FAIL: gcc.dg/format/c99-printf-1.c
FAIL: gcc.dg/format/ext-1.c
FAIL: gcc.dg/format/ext-3.c 
FAIL: gcc.dg/format/ext-6.c 
FAIL: gcc.dg/noncompile/voidparam-1.c
FAIL: gcc.dg/typespec-1.c
FAIL: g++.law/visibility19.C

and the failures usually are marked with 'test for warnings'
or 'test for excess errors', e.g.

FAIL: gcc.dg/format/ext-3.c bad %^# (test for warnings, line 215)
FAIL: gcc.dg/format/ext-3.c (test for excess errors) 

See also
http://gcc.gnu.org/ml/gcc/2001-02/msg01313.html
http://gcc.gnu.org/ml/gcc/2002-09/msg00653.html
http://mail.gnu.org/archive/html/dejagnu/2003-07/msg00020.html

One workaround might be to install the latest expect, but 
I haven't tried that.
FWIW, on one system I'm seeing this on, 'expect -version' outputs
"expect version 5.32.2"
which is probably as old as the oldest report I cite above,
so updating expect might indeed help.


             reply	other threads:[~2003-08-28 17:33 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-28 17:33 dank at kegel dot com [this message]
2003-11-02 22:37 ` [Bug other/12096] " pinskia at gcc dot gnu dot org
2003-11-02 22:51 ` jsm at polyomino dot org dot uk
2003-11-03  0:36 ` dank at kegel dot com
2003-11-03  1:51 ` pinskia at gcc dot gnu dot org
2003-11-03  2:35 ` pinskia at gcc dot gnu dot org
2003-11-05  0:39 ` dhazeghi at yahoo dot com
2004-01-17 23:57 ` dhazeghi at yahoo dot com
2004-01-24  6:08 ` markkp at msm dot umr dot edu
2004-01-27 17:09 ` dank at kegel dot com
2004-01-27 17:19 ` jsm at polyomino dot org dot uk
2004-01-27 17:36 ` dhazeghi at yahoo dot com
2004-01-28 16:47 ` pinskia at gcc dot gnu dot org
2005-02-08 18:49 ` chris at bubblescope dot net
2005-06-10 15:35 ` themis_hv at yahoo dot co dot uk

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=20030828173345.12096.dank@kegel.com \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).