Away from laptop right now, but the trace can be printed using
logger.exception(). Not sure where to insert it, but that is the key method.
On Mar 14, 2012 11:12 AM, "Philip Martin" <philip_at_codematters.co.uk> wrote:
> Philip Martin <philip_at_codematters.co.uk> writes:
> > Philip Martin <philip.martin_at_wandisco.com> writes:
> >> Philip Martin <philip.martin_at_wandisco.com> writes:
> >>> Hyrum K Wright <hyrum.wright_at_wandisco.com> writes:
> >>>> Agreed that the stack trace is important here. Do you know in which
> >>>> revision it disappeared?
> >>> When I sync'd the branch with the trunk :-P
> >>> I'll have a look.
> >> r1297676 produces a Python stack trace, r1297712 does not.
> > Ooops! r1297676 is just an error in the testsuite, not a stack trace
> > for a failing test.
> So it's really r1297661 that produces a Python stack trace:
> svn: warning: W160040: No lock on path '/iota' in filesystem
> Traceback (most recent call last):
> line 1323, in run
> rc = self.pred.run(sandbox)
> line 176, in run
> return self.func(sandbox)
> File "../../../../src2/subversion/tests/cmdline/lock_tests.py", line 338,
> in handle_defunct_lock
> r1297676 doesn't run properly and r1297712 has no stack trace.
Received on 2012-03-14 17:48:09 CET