On Tue, Mar 15, 2011 at 09:56, Kamil Dudka <kdudka_at_redhat.com> wrote:
> On Tuesday 15 March 2011 08:23:51 Tor Arntsen wrote:
>> It's a bit unfortunate with build problems because it prevents using
>> git-bisect to find where runtime problems/bugs happened, or at least
>> it makes it tricky (git-bisect still works fabulously for finding
>> build errors of course..)
>
> If you are bisecting by hand, use git bisect skip.  If you are using
> a script, just return exit code 125 whenever a build failure happens.

Skipping the build failure isn't the problem, the problem is when a
feature/change was introduced in a commit that is inside a range of
commits with build failures.. then, later, when a build correction is
commited and the runtime failure surfaces you won't be able to find
the precise commit which introduced the runtime failure (unless you
patch every commit in the range of commits with build failures so that
they build.. not always a safe or easy option).

-Tor

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2011-03-15