From: Manfred.Hollstein@ks.sel.alcatel.de
To: schmid@ltoi.iap.physik.tu-darmstadt.de
Cc: egcs@cygnus.com
Subject: Re: new FAILs in the g++ testsuite?
Date: Thu, 29 Jan 1998 23:31:00 -0000 [thread overview]
Message-ID: <9801300729.AA28257@lts.sel.alcatel.de> (raw)
In-Reply-To: <Pine.A32.3.95.980129184102.13911A-100000@ltoi.iap.physik.tu-darmstadt.de>
On Thu, 29 January 1998, 18:43:34, schmid@ltoi.iap.physik.tu-darmstadt.de wrote:
> While examining the file g++.log for the FAILs of the g++ testsuite I
> found strange logging messages.
> There are FAIls without an explanation.
> They do not count in the g++ summary.
>
Even worse: on my m88k-motorola-sysv3 system various libio and
libstdc++ tests failed with dejagnu-971222; running those tests
manually showed there is _no_ error! Switching back to dejagnu-971028
cured this problem for me.
BTW, the 971028's .log file format was IMHO much better and obvious.
Manfred
prev parent reply other threads:[~1998-01-29 23:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-29 13:44 Peter Schmid
1998-01-29 23:31 ` Manfred.Hollstein [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=9801300729.AA28257@lts.sel.alcatel.de \
--to=manfred.hollstein@ks.sel.alcatel.de \
--cc=egcs@cygnus.com \
--cc=schmid@ltoi.iap.physik.tu-darmstadt.de \
/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).