From: Alexandre Oliva <oliva@dcc.unicamp.br>
To: egcs@cygnus.com
Cc: manson@cygnus.com
Subject: Re: Results for haifa-enabled egcs-971206 gcc testsuite on i586-pc-linux-gnulibc1
Date: Wed, 17 Dec 1997 21:57:00 -0000 [thread overview]
Message-ID: <or67onff5n.fsf@grupiara.dcc.unicamp.br> (raw)
In-Reply-To: <orbtyodewk.fsf@grupiara.dcc.unicamp.br>
Alexandre Oliva writes:
> Jason Merrill writes:
>> The results Alexandre sends out are useful for knowing the state of various
>> ports, but not for fixing the bugs. Might it be possible for dejagnu to
>> include the log of each failure, but not each success, in some file that he
>> could send in instead?
> I'm pretty sure I can hack an awk script that will search the log file
> for failures and unexpected successes, and print that all.
Oh well, seems like I spoke too soon. The format of the log file is
not what I expected it to be: only some error messages are printed
after the FAIL line, and I just can't backtrack in an awk script :-(
If only dejagnu printed those errors after the FAIL line...
> Jason, is there any change you get the `make check' rules into the FSF
^ this should have read `chance'
> gcc main Makefile? This would make my life much easier!
--
Alexandre Oliva
mailto:oliva@dcc.unicamp.br mailto:aoliva@acm.org
http://www.dcc.unicamp.br/~oliva
Universidade Estadual de Campinas, SP, Brasil
next prev parent reply other threads:[~1997-12-17 21:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199712100646.EAA16778.cygnus.egcs@pinheiros.dcc.unicamp.br>
1997-12-10 10:46 ` Jason Merrill
1997-12-10 15:45 ` Alexandre Oliva
1997-12-17 21:57 ` Alexandre Oliva [this message]
1997-12-09 22:51 Alexandre Oliva
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=or67onff5n.fsf@grupiara.dcc.unicamp.br \
--to=oliva@dcc.unicamp.br \
--cc=egcs@cygnus.com \
--cc=manson@cygnus.com \
/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).