-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Karma: cannot start chrome #1662
Karma: cannot start chrome #1662
Comments
Can you try without coverage activated? |
Yes I tried by removing them in karma.conf.js (as below) and started karma but still I'm getting same issue.I hope uninstall coverage doesn't make sense. |
I am getting the same error with Karma v0.13.22 and Chrome 50: 07 06 2016 12:03:25.680:INFO [Chrome 50.0.2661 (Windows 7 0.0.0)]: Connected on If I remove Chrome from the list of browsers in karma.conf.js, then the tests run successfully in Firefox. |
Looks like in https://github.com/karma-runner/karma/blob/v0.13.22/lib/reporters/progress.js#L51 |
Just came across this bug as well. Weirdly enough, this started happening once I turned Here's my config: var _ = require('lodash');
var webpackCommonConfig = require('./webpack.common.js');
module.exports = function(config) {
config.set({
basePath: 'tests',
frameworks: ['jasmine'],
files: [
'../src/utils/intl_polyfill.js',
'*.spec.js'
],
exclude: [],
preprocessors: {
'../src/*.js': ['webpack'],
'../src/**/*.js': ['webpack'],
'../locales/*.js': ['webpack'],
'*.spec.js': ['webpack'],
'*Data.js': ['webpack']
},
webpack: _.merge({
devtool: 'inline-source-map'
}, webpackCommonConfig),
webpackMiddleware: {
stats: 'errors-only'
},
reporters: ['progress'],
port: 9876,
colors: true,
logLevel: config.LOG_ERROR,
autoWatch: false,
browsers: ['PhantomJS'],
singleRun: false,
concurrency: Infinity
})
} |
ping |
It seems like this issue is fixed for me now, when using
karma and karma-webpack had updates since the version I set on my package.json so I assume one of them fixed the issue. |
I have simple use case which reproduce this problem on macOs: mkdir foo
cd foo
node --version #v7.3.0
npm install [email protected]
npm install -g karma-cli
karma init # Chrome, jasmine
npm install jasmine-core
# [email protected]
# [email protected]
karma start
# In opened Chrome reload page (cmd+r) Note: If onRunStart does not called then this._browser is not initialized, but when you reload page in chrome |
Was this ever resolved? Same issue. Why was this closed? |
I did not found decision too :( |
@wvicioso @Dok11 we fixed javascript exception in karma
It doesn't fix the reason why Chrome doesn't start because in 90% it's environment problem or problem in karma-chrome-launcher. |
For my angularjs project, trying to use karma+jamine for unit testing. I have installed karma @ local and trying to start from .bin folder. So i'm getting following issue; FYI I'm pasting folder structure along with,
The text was updated successfully, but these errors were encountered: