From: Daniel Jacobowitz <drow@mvista.com>
To: George France <france@handhelds.org>
Cc: gdb@sources.redhat.com, clp@iol.unh.edu
Subject: Re: exit status of 'make check'
Date: Tue, 13 Nov 2001 10:05:00 -0000 [thread overview]
Message-ID: <20011125135448.A16810@nevyn.them.org> (raw)
In-Reply-To: <01112513400901.05740@shadowfax.middleearth>
On Sun, Nov 25, 2001 at 01:40:09PM -0500, George France wrote:
> We are not discussing, the results of 'runtest'. We are discussing the
> results of 'make check'. Here is another simple example, On 2001-11-22, I
> built the gcc_3.0.2 HEAD branch. 'make check' returned a zero for an exit
> code, but many of the testsuites FAILed.
GCC does this by completely ignoring the exit code of runtest; in other
words, make check will always succeed. I don't think that's an
acceptable step. Do you?
We are discussing the result of runtest, because the DejaGNU
maintainers are the appropriate people to set policy for this sort of
thing.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2001-11-25 18:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-11 10:33 Michael Elizabeth Chastain
2001-11-11 11:30 ` George France
2001-11-11 22:14 ` Daniel Jacobowitz
2001-11-12 15:02 ` George France
2001-11-13 8:47 ` Daniel Jacobowitz
2001-11-13 9:53 ` George France
2001-11-13 10:05 ` Daniel Jacobowitz [this message]
2001-11-13 10:26 ` George France
2001-11-25 20:59 ` George France
-- strict thread matches above, loose matches on Subject: below --
2001-11-13 10:34 Michael Elizabeth Chastain
2001-11-13 12:38 ` George France
2001-11-25 22:21 ` George France
2001-11-25 21:11 ` Michael Elizabeth Chastain
2001-11-10 10:17 George France
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=20011125135448.A16810@nevyn.them.org \
--to=drow@mvista.com \
--cc=clp@iol.unh.edu \
--cc=france@handhelds.org \
--cc=gdb@sources.redhat.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