[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Call stack with new testsuite logging?

From: Hyrum K Wright <hyrum.wright_at_wandisco.com>
Date: Wed, 14 Mar 2012 14:07:22 -0500

On Wed, Mar 14, 2012 at 12:48 PM, Branko Čibej <brane_at_apache.org> wrote:
> On 14.03.2012 17:08, Hyrum K Wright wrote:
>> On Wed, Mar 14, 2012 at 10:47 AM, Greg Stein <gstein_at_gmail.com> wrote:
>>> 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.
>> logger.execption() always logs at the ERROR level, and we (I?) are
>> aiming to keep test failure output logging at the WARN level (ERROR is
>> reserved for errors in the test suite itself).
>> svntest.main._log_exception() will log at the WARN level.
> Any logging call will print the exception info and stack trace if given
> the keyword parameter exc_info=True. You do not need the traceback
> module, you do not have to call sys.exc_info().

Thanks for the insight. Updated in r1300688.


uberSVN: Apache Subversion Made Easy
Received on 2012-03-14 20:07:55 CET

This is an archived mail posted to the Subversion Dev mailing list.