Re: Debugging hash contents

Philip Martin wrote:

> One reason the tests might fail outside the test-suite is if your
> .subversion/config has an effect, the test-suite uses --config-dir.

That's backwards; the tests only fail _inside_ the test-suite. I cannot
figure out why the use of --config-dir would cause the keywords hash
from being populated (which is why I wanted to peek at the hash contents).

>
> Just in case you don't know this already: it's possible to run the
> python tests individually.
>
> $ cd subversion/tests/clients/cmdline
> $ path/to/trans_tests.py -v 1
>
> That lets you identify the bit that fails, you can then edit
> trans_tests.py to make it stop before the failure, rerun it and
> finally run the command that fails manually.
>

Yes, I did know that I could run the tests individually, though I didn't
know about the -v flag. That gives me more information, thanks! I'll
prepare a patch to the tests README file describing the usage of -v to
produce verbose output (since I don't see any place that is mentioned).

> It could be incorrect memory use. On Linux some of these can be
> detected by enabling APR's pool debugging and running the client under
> valgrind.

I think it is highly unlikely to be problems with the pool, because as I
said, it works fine outside of the test-suite directories.

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org