debug output by default is too spammy

[Paul Larson]

We should not be spitting out debug output by default. Please add a debug flag or something like that, and only put this output in when requested.

[Zygmunt Krynicki (zyga)]

I've somewhat fixed that in lava-too. I need to publish that branch. My branch allows you to setup debugging/verbose mode from command line. That propagates sensibly to individual Commands.

[Zygmunt Krynicki (zyga)]

ChiThu, make sure that lava-test uses logging.info() for stuff that you want do display when running with --verbose flag and logging.debug() for the stuff you want to see while debugging. For debugging make sure you use logging.getLogger("some-fancy-name") to get a logger instance and log via that instance. I've added code for lava-tool to turn on an arbitrary list of debugging loggers.

[Le Chi Thu (le-chi-thu)]

ok

/Chi Thu

On 7 February 2012 15:14, Zygmunt Krynicki
<email address hidden> wrote:
> ChiThu, make sure that lava-test uses logging.info() for stuff that you
> want do display when running with --verbose flag and logging.debug() for
> the stuff you want to see while debugging. For debugging make sure you
> use logging.getLogger("some-fancy-name") to get a logger instance and
> log via that instance. I've added code for lava-tool to turn on an
> arbitrary list of debugging loggers.
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/928522
>
> Title:
>  debug output by default is too spammy
>
> Status in LAVA Automated Testing Framework:
>  New
> Status in LAVA Command-line Tool:
>  In Progress
>
> Bug description:
>  We should not be spitting out debug output by default.  Please add a
>  debug flag or something like that, and only put this output in when
>  requested.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/lava-test/+bug/928522/+subscriptions