From: Michael Elizabeth Chastain <mec@shout.net>
To: drow@mvista.com, france@handhelds.org
Cc: clp@iol.unh.edu, gdb@sources.redhat.com
Subject: Re: exit status of 'make check'
Date: Tue, 13 Nov 2001 10:34:00 -0000 [thread overview]
Message-ID: <200111260510.XAA27776@duracef.shout.net> (raw)
I agree with Daniel here, but from a different point of view.
It would be nice if the exit status was, for example:
0 no results are ERROR, WARNING, or FAIL
1 no results are ERROR or WARNING; some results are FAIL
2 some results are ERROR or WARNING
3 the test harness did not run well enough to generate results
(e.g. runtest not found).
(or something like that)
To achieve this result, someone would have to: design a set of exit statuses,
build consensus for it among several user communities, and submit patches to
tools like dejagnu.
That's a lot of work. For the same amount of work, one could implement other
useful features in the test machinery and in the test suite itself. For
instance, I would like to have ERRORs and WARNINGs reported with the test
script filename in them, just like FAILs are.
I do sympathize that the exit status is imprecise and that this can
interfere with large-scale automation.
Michael C
WARNING: multiple messages have this Message-ID
From: Michael Elizabeth Chastain <mec@shout.net>
To: drow@mvista.com, france@handhelds.org
Cc: clp@iol.unh.edu, gdb@sources.redhat.com
Subject: Re: exit status of 'make check'
Date: Sun, 25 Nov 2001 21:11:00 -0000 [thread overview]
Message-ID: <200111260510.XAA27776@duracef.shout.net> (raw)
Message-ID: <20011125211100.7709qqaukRcFYSDa24v0TIsFtheUs49Fj6bcRsmxov4@z> (raw)
I agree with Daniel here, but from a different point of view.
It would be nice if the exit status was, for example:
0 no results are ERROR, WARNING, or FAIL
1 no results are ERROR or WARNING; some results are FAIL
2 some results are ERROR or WARNING
3 the test harness did not run well enough to generate results
(e.g. runtest not found).
(or something like that)
To achieve this result, someone would have to: design a set of exit statuses,
build consensus for it among several user communities, and submit patches to
tools like dejagnu.
That's a lot of work. For the same amount of work, one could implement other
useful features in the test machinery and in the test suite itself. For
instance, I would like to have ERRORs and WARNINGs reported with the test
script filename in them, just like FAILs are.
I do sympathize that the exit status is imprecise and that this can
interfere with large-scale automation.
Michael C
next reply other threads:[~2001-11-26 5:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-13 10:34 Michael Elizabeth Chastain [this message]
2001-11-13 12:38 ` George France
2001-11-25 22:21 ` George France
2001-11-25 21:11 ` Michael Elizabeth Chastain
-- strict thread matches above, loose matches on Subject: below --
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
2001-11-13 10:26 ` George France
2001-11-25 20:59 ` George France
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=200111260510.XAA27776@duracef.shout.net \
--to=mec@shout.net \
--cc=clp@iol.unh.edu \
--cc=drow@mvista.com \
--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