|Subject:||WC detritus could skew results|
This is just an observation/feature request based on my usage of this module. Subversion has this "feature" whereby if you downgrade to an earlier revision where certain files/directories didn't exist, then when you attempt an upgrade to a later revision after they've been created, it will complain with something like this: svn: Failed to add directory 'blah': object of the same name already exists. Thus, when doing a binary search through revisions, some updates may not accurately reflect the state of the repository at a particular revision. Also, the test program that determines which revision affected a change may create spurious files in the working copy that are present during subsequent runs and these files may affect the output of the test program. The only guaranteed fix that I see right now is to always checkout pristine revisions rather than using "svn up" to move a single WC from revision to revision.