From: Christian Couder <chriscool@tuxfamily.org>
To: Benoit SIGOURE <tsuna@lrde.epita.fr>
Cc: git list <git@vger.kernel.org>
Subject: Re: [PATCH] Bisect run: "skip" current commit if script exit code is 125.
Date: Sat, 27 Oct 2007 07:02:31 +0200 [thread overview]
Message-ID: <200710270702.31923.chriscool@tuxfamily.org> (raw)
In-Reply-To: <A43880E9-E496-48AA-BC1C-2C98DFD12370@lrde.epita.fr>
Le vendredi 26 octobre 2007, Benoit SIGOURE a écrit :
> On Oct 26, 2007, at 5:39 AM, Christian Couder wrote:
> >
> > +The special exit code 125 should be used when the current source code
> > +cannot be tested. If the "run" script exits with this code, the
> > current
> > +revision will be "skip"ped, see `git bisect skip` above.
> > [...]
>
> Since exit 77 is already used by automake to mean "skip", wouldn't it
> be better to do the same thing here?
I don't think 77 is better, first because for automake this is to ignore
some non portable test results "in environments where they don't make
sense", so if we "bisect run" the same test script and it returns 77 once,
it will probably returns 77 everytime because the environment will not have
changed after a new revision has been checked out.
Also there is:
$ grep 77 /usr/include/sysexits.h
#define EX_NOPERM 77 /* permission denied */
and a search for "include <sysexits.h>" in http://www.google.com/codesearch
returns a lot of results.
Christian.
next prev parent reply other threads:[~2007-10-27 4:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-26 3:39 [PATCH] Bisect run: "skip" current commit if script exit code is 125 Christian Couder
2007-10-26 6:25 ` Benoit SIGOURE
2007-10-27 5:02 ` Christian Couder [this message]
[not found] ` <20071027052834.GA3115@hermes.priv>
2007-10-27 5:33 ` Tom Prince
2007-10-27 6:12 ` Junio C Hamano
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=200710270702.31923.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=tsuna@lrde.epita.fr \
/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 NNTP newsgroup(s).