[asterisk-dev] Asterisk Test Suite: Proposed Logging Change

Mark Michelson mmichelson at digium.com
Mon Dec 9 09:39:59 CST 2013


> Matthew Jordan <mailto:mjordan at digium.com>
> Sunday, December 08, 2013 9:09 AM
> Back when we first added python logging to the Asterisk Test Suite, 
> there were considerably fewer tests and the log files - while large - 
> were slightly more manageable. Today, it feels like things have gotten 
> a bit more cumbersome.
>
> On a recent run of the full Asterisk Test Suite, the full DEBUG output 
> can top out at over 11MB. While not so huge that it is impossible to 
> deal with, that's still quite large.
>
> How would everyone who uses the Test Suite feel if each test created 
> its own DEBUG Python logs and stored them in the same location as the 
> test's Asterisk log files? From the perspective of someone trying to 
> figure out why a test failed, it would be a bit easier to look in 
> those locations (as you usually have to anyway to look at the Asterisk 
> logs), and it doesn't preclude using the logger.conf for the Python 
> logger to create a central location for log files.
>
> Matt
>
I'm 100% behind this. Whenever I step away from testsuite development 
for a while, I initially search for Python logs in the path where the 
test's Asterisk logs are stored. Now my instinct will actually guide me 
to the proper location.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20131209/20bdd7fc/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: postbox-contact.jpg
Type: image/jpeg
Size: 1143 bytes
Desc: not available
URL: <http://lists.digium.com/pipermail/asterisk-dev/attachments/20131209/20bdd7fc/attachment.jpg>


More information about the asterisk-dev mailing list