From: Christian Couder <chriscool@tuxfamily.org>
To: "A B" <gentosaker@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git bisect on multiple cores
Date: Wed, 9 Apr 2008 06:29:28 +0200 [thread overview]
Message-ID: <200804090629.29122.chriscool@tuxfamily.org> (raw)
In-Reply-To: <dbbf25900804080358o6b1ada20pfb94f68f06a23f83@mail.gmail.com>
Le mardi 8 avril 2008, A B a écrit :
> 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.
next prev parent reply other threads:[~2008-04-09 4:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-08 10:58 git bisect on multiple cores A B
2008-04-08 12:50 ` David Symonds
2008-04-08 18:50 ` Junio C Hamano
2008-04-09 4:29 ` Christian Couder [this message]
2008-04-09 5:47 ` Christian Couder
2008-04-09 7:17 ` Karl Hasselström
2008-04-09 8:07 ` Matthieu Moy
2008-04-09 8:27 ` Karl Hasselström
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=200804090629.29122.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=gentosaker@gmail.com \
--cc=git@vger.kernel.org \
/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