[QUESTION] How can I reduce log verbosity? about karma-sauce-launcher

[Jonahss]

You could submit a Pull Request to have that log line respect the karma
error-level configuration.

On Fri, Mar 6, 2015 at 6:48 AM, Iliyan Peychev [email protected]
wrote:

Hello,

Is it possible to reduce the log verbosity? We run our tests via Travis
and it complains https://travis-ci.org/alloyui/core/builds/53331790
that the log is too big. We have specified LOG_ERROR level in karma config
file, but it seems it is not being taken in consideration, because there
are a lot of messages https://travis-ci.org/alloyui/core/builds/53331790
like:

Safari 5.1.7 (Windows 7): Executed 87 of 306 SUCCESS (0 secs / 0.031 secs)
SUCCESS (2.708 secs / 0.975 secs)
Safari 5.1.7 (Windows 7): Executed 88 of 306 SUCCESS (0 secs / 0.032 secs)
SUCCESS (2.708 secs / 0.975 secs)
Safari 5.1.7 (Windows 7): Executed 89 of 306 SUCCESS (0 secs / 0.032 secs)

Looking in the code here
https://github.com/karma-runner/karma-sauce-launcher/blob/master/lib/sauce_connect.js#L11
it seems the log level is debug. Is there a way to change this?

Thanks,

—
Reply to this email directly or view it on GitHub
#67.

[Krinkle]

The progress indication of the test execution is not provided by karma-sauce-launcher. And even in Karma's main output, that is not related to "debug" level output.

The default reporter is progress, which prints a line for each update. If possible it replaces the previous line, but when streaming output (such as for logs of Jenkins or Travis CI) that doesn't work.

Consider using the dots reporter instead.

See "reporters" on http://karma-runner.github.io/0.12/config/configuration-file.html

[ipeychev]

Thanks, makes sense.