Re: [PATCH] Display stderr before throwing exception in the python test suite

On 1/2/07, Daniel Rall <dlr@collab.net> wrote:
> When dealing with segfaults like this, I usually run just that test in
> --verbose mode, figure out what line it's failing on based on the
> output, re-run the test with a local edit which makes it stop before
> attempting the behavior that segfaults (performing the set up for me),
> then run just the failing command in the debugger.

Yah, same thing here. (Except I don't both to edit the tests tho. I
just have to read the tests to figure out how to produce the same
sequence and create a batch script which sets it up...)

> Something which simplified this process would be great. With some
> tests, there's sometimes not enough output to determine exactly where
> a failure occurs with a println-based binary search through the test.

Perhaps a way to tell the test framework to run X commands before
stopping? And, have --verbose print the number for each command?
i.e. it could fail on 'command' 1512, and you could pass it
--stop-at=1512 or something. A thought. -- justin

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jan 2 23:44:36 2007