From: Jeffrey A Law <law@cygnus.com>
To: Alexandre Oliva <oliva@dcc.unicamp.br>
Cc: Joe Buck <jbuck@synopsys.com>,
Matthias.Klose@cs.tu-berlin.de, egcs@cygnus.com
Subject: Re: [patch] Re: How to generate test reports?
Date: Fri, 19 Jun 1998 06:07:00 -0000 [thread overview]
Message-ID: <10728.898245350@hurl.cygnus.com> (raw)
In-Reply-To: <orhg2ebcv0.fsf@zecarneiro.lsd.dcc.unicamp.br>
> > Next step, tie them into the Makefile :-)
>
> I'm not sure this is what you have in mind, is it?
It's a reasoanble start. I really hadn't thought it through yet.
Basically I think we need a make target which does all the right things
so long term we might want to have make bootstrap dump its output onto
both stdout and into a suitable file for later processing. Just
not sure.
> for top-level ChangeLog:
>
> * Makefile.in (local-clean): remove *.log
> (warning.log): built with warn_summary from build.log
> (mail-report.log): run test_summary
> (mail-report-with-warnings.log): run test_summary including
> warning.log in the report
>
> for contrib/ChangeLog:
>
> * test_summary: new switch (-i) and environment variable
> (append_logs) for including files in the report.
I think you should install this patch. If we decide to change directions
later we can always remove it.
jeff
next prev parent reply other threads:[~1998-06-19 6:07 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-05-12 8:13 Matthias Klose
1998-05-12 12:36 ` Jeffrey A Law
1998-05-13 0:56 ` Matthias Klose
1998-05-13 1:47 ` Jeffrey A Law
1998-05-13 7:22 ` Robert Lipe
1998-05-13 7:22 ` Alexandre Oliva
1998-05-13 10:04 ` Joe Buck
1998-05-13 20:23 ` Joe Buck
1998-05-15 1:48 ` Alexandre Oliva
1998-05-20 22:55 ` Jeffrey A Law
1998-05-21 20:15 ` Alexandre Oliva
1998-05-23 22:47 ` Jeffrey A Law
1998-05-25 10:57 ` [patch] " Alexandre Oliva
1998-06-19 6:07 ` Jeffrey A Law [this message]
1998-06-19 6:07 ` Jeffrey A Law
1998-06-22 17:41 ` Alexandre Oliva
1998-05-21 20:15 ` Matthias Klose
1998-05-14 11:50 ` Joe Buck
1998-05-13 1:58 ` Alexandre Oliva
1998-05-12 18:04 ` 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=10728.898245350@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=Matthias.Klose@cs.tu-berlin.de \
--cc=egcs@cygnus.com \
--cc=jbuck@synopsys.com \
--cc=oliva@dcc.unicamp.br \
/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).