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.
|
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-dev