logLevel in config file is not honored

[christothes]

Running Karma v0.10.4 with a logLevel of: config.LOG_ERROR and all my console.info logs are displaying in the output console running Karma.

[vojtajina]

This works for me. Just tried v0.10.4, latest stable (0.10.6 and master). Are you sure you are not overriding it from CLI or something?

Can you share your karma.conf.js?

[christothes]

I'm not aware of any override I may be doing.

config file is:

module.exports = function (config) {
    config.set({

    // base path, that will be used to resolve files and exclude
    basePath: '',


    // frameworks to use
    frameworks: ['jasmine'],


    // list of files / patterns to load in the browser
    files: [
        'public/javascripts/libs/angular.js',
        'public/javascripts/libs/angular-mocks.js',
        'public/javascripts/libs/angular-route.js',
        'public/javascripts/app/*.js'

    ],


    // list of files to exclude
    exclude: [

    ],


    // test results reporter to use
    // possible values: 'dots', 'progress', 'junit', 'growl', 'coverage'
    reporters: ['progress'],


    // web server port
    port: 9876,


    // enable / disable colors in the output (reporters and logs)
    colors: true,


    // level of logging
    // possible values: config.LOG_DISABLE || config.LOG_ERROR || config.LOG_WARN || config.LOG_INFO || config.LOG_DEBUG
    logLevel: config.LOG_ERROR,


    // enable / disable watching file and executing tests whenever any file changes
    autoWatch: true,


    // Start these browsers, currently available:
    // - Chrome
    // - ChromeCanary
    // - Firefox
    // - Opera (has to be installed with `npm install karma-opera-launcher`)
    // - Safari (only Mac; has to be installed with `npm install karma-safari-launcher`)
    // - PhantomJS
    // - IE (only Windows; has to be installed with `npm install karma-ie-launcher`)
    browsers: ['Chrome'],


    // If browser does not capture in given timeout [ms], kill it
    captureTimeout: 60000,


    // Continuous Integration mode
    // if true, it capture browsers, run tests and exit
    singleRun: false
    });
};

[vojtajina]

Oh, are you talking about console.log stuff from the browser?
That is actually a different thing. There is an issue talking about possiblity of merging these two things, see #480

[christothes]

yes, I was assuming that the logLevel setting would suppress these according to the level specified. I could have sworn that in previous versions all my console.info output was being suppressed.

[vojtajina]

All right, then this is a duplicate of #480, closing...