So you're saying put the logs/full.txt and logs/messages.txt files in the
/tmp/asterisk-testsuite path, and only copy them down to the
logs/test/path/*.txt on a failure?
On Sun, Dec 8, 2013 at 9:09 AM, Matthew Jordan mjor...@digium.com wrote:
Back when we first added python logging to the
Matthew Jordan
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
On Sun, 2013-12-08 at 09:09 -0600, Matthew Jordan wrote:
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
On Mon, Dec 9, 2013 at 9:32 AM, Scott Griepentrog
sgriepent...@digium.comwrote:
So you're saying put the logs/full.txt and logs/messages.txt files in the
/tmp/asterisk-testsuite path, and only copy them down to the
logs/test/path/*.txt on a failure?
Kind of.
Currently, the python
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
