binary search utility script

Hello.

I wrote a binary search script (in perl) for working against a
checked out svn repository to help track down some failures on a
project. Someone suggested I clean it up and submit to the dev list
here for inclusion in the tools directory.

Before I went to a lot of trouble to make it more generic (less
hardcoding, less unix-isms), I wanted to bounce the description off
the list and see if there was interest. Or if I was missing some
crucial must-have feature.

Currently, it requires:

- you have a project checked out (no local mods is recommended)
- that you provide a command line script that can test a particular
bug/feature. (including cleaning/building your project if necessary)
- start/end versions

And it assumes:

- that a binary search is actually warranted - if the behavior flip
flops, all bets are off.

And it does:

- an svn up to the edge case versions
   - runs your script
   - and stores the output (STDOUT; STDERR is logged, but not used in
comparisons)
- then begins a binary search: Depending on the output of the
intermediate versions, the search area is confined one way or the
other. for each version, your script is run, and the output stored.

Finally, it outputs (hopefully) something like:

*** changed between r11402 and r11403

(or, squawks about how some rev generated bad output - unlike the two
edge cases.)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Feb 7 17:13:24 2006