Re: [PATCH] Bisect run: "skip" current commit if script exit code is 125.

From: Christian Couder <chriscool@tuxfamily.org>
Date: Oct 27, 2007, 05:02 UTC
Message-ID: <200710270702.31923.chriscool@tuxfamily.org>
In-Reply-To: <A43880E9-E496-48AA-BC1C-2C98DFD12370@lrde.epita.fr>

Le vendredi 26 octobre 2007, Benoit SIGOURE a écrit :

Show 10 quoted lines

> 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.