Re: git bisect on multiple cores

From: Christian Couder <chriscool@tuxfamily.org>
Date: Apr 9, 2008, 04:29 UTC
Message-ID: <200804090629.29122.chriscool@tuxfamily.org>
In-Reply-To: <dbbf25900804080358o6b1ada20pfb94f68f06a23f83@mail.gmail.com>

Le mardi 8 avril 2008, A B a écrit :

Show 6 quoted lines

> git bisect is really cool. I use it for the first time.
> Just a thought, if you have a multiple core computer, can't you make
> git build new versions in the background while testing the previuos
> version? Alright, if you build 2 versions, one of them will never be
> tested, but you will perhaps save some time by letting it build in the
> background?

Yes, you can do that.

If you have cloned your repository twice (or more), then you can bisect compile and test at the same time in your 3 repositories (or more if you really want).

For example if bisecting in one repo asks you to test revision X, then you can bisect and then build (and even maybe start testing) in another repo assuming revision X is good, and in yet in another one assuming revision X is bad.

(In the repo where you assume X is good you use:

"git bisect start CURRENT-BAD X"

and in the third one, where you assume X is bad, you use:

"git bisect start X CURRENT-GOOD")

When you know that X was good then you can kill the build or test processes and "git bisect reset" in the repository where you assumed wrongly X was bad. You can then assume something else with "git bisect start B G" and build and test in this repo again.

In the repo that told you X was good, then you need only to use "git bisect good" or "git bisect bad" without building and testing to assume something about the revision that should be built and tested.

Regards, Christian.