5
Debug Log:Karma błąd - Chrome nie zostały ujęte w 60000 ms, zabijając
E:\Projects\abb\Projects\WebApp\abb.web>karma start
DEBUG [plugin]: Loading karma-* from E:\Projects\abb\Projects\WebApp\abb
.web\node_modules
DEBUG [plugin]: Loading plugin E:\Projects\abb\Projects\WebApp\abb.web\n
ode_modules/karma-chrome-launcher.
DEBUG [plugin]: Loading plugin E:\Projects\abb\Projects\WebApp\abb.web\n
ode_modules/karma-jasmine.
INFO [karma]: Karma v0.12.16 server started at http://localhost:9876/
INFO [launcher]: Starting browser Chrome
DEBUG [temp-dir]: Creating temp dir at C:\Users\Kunal\AppData\Local\Temp\karma-8
6563066
DEBUG [launcher]: C:\Program Files (x86)\Google\Chrome\Application\chrome.exe --
user-data-dir=C:\Users\Kunal\AppData\Local\Temp\karma-86563066 --no-default-brow
ser-check --no-first-run --disable-default-apps --disable-popup-blocking --disab
le-translate http://localhost:9876/?id=86563066
DEBUG [watcher]: Resolved files:
E:/Projects/abb/Projects/WebApp/abb.web/node_modules/karma-jasmi
ne/lib/jasmine.js
E:/Projects/abb/Projects/WebApp/abb.web/node_modules/karma-jasmi
ne/lib/adapter.js
E:/Projects/abb/Projects/WebApp/abb.web/app/js/vendor/angular.js
E:/Projects/abb/Projects/WebApp/abb.web/app/js/vendor/angular-ro
ute.js
E:/Projects/abb/Projects/WebApp/abb.web/test/lib/angular-mocks.j
s
E:/Projects/abb/Projects/WebApp/abb.web/app/js/app.debug.js
E:/Projects/abb/Projects/WebApp/abb.web/test/unit/homepage.spec.
js
DEBUG [web-server]: serving: E:\Projects\abb\Projects\WebApp\abb.web\nod
e_modules\karma\static/client.html
DEBUG [web-server]: serving: E:\Projects\abb\Projects\WebApp\abb.web\nod
e_modules\karma\static/karma.js
DEBUG [web-server]: upgrade /socket.io/1/websocket/9uv4dB4yQPjZ7sZcWUuH
DEBUG [karma]: A browser has connected on socket 9uv4dB4yQPjZ7sZcWUuH
WARN [launcher]: Chrome have not captured in 60000 ms, killing.
DEBUG [launcher]: Process Chrome exited with code 0
DEBUG [temp-dir]: Cleaning temp dir C:\Users\Kunal\AppData\Local\Temp\karma-8656
3066
INFO [launcher]: Trying to start Chrome again (1/2).
DEBUG [launcher]: Restarting Chrome
DEBUG [temp-dir]: Creating temp dir at C:\Users\Kunal\AppData\Local\Temp\karma-8
6563066
DEBUG [launcher]: C:\Program Files (x86)\Google\Chrome\Application\chrome.exe --
user-data-dir=C:\Users\Kunal\AppData\Local\Temp\karma-86563066 --no-default-brow
ser-check --no-first-run --disable-default-apps --disable-popup-blocking --disab
le-translate http://localhost:9876/?id=86563066
DEBUG [web-server]: serving: E:\Projects\abb\Projects\WebApp\abb.web\nod
e_modules\karma\static/client.html
DEBUG [web-server]: serving: E:\Projects\abb\Projects\WebApp\abb.web\nod
e_modules\karma\static/karma.js
DEBUG [web-server]: upgrade /socket.io/1/websocket/ei81-LVHlsfeDeCXWUuI
DEBUG [karma]: A browser has connected on socket ei81-LVHlsfeDeCXWUuI
WARN [launcher]: Chrome have not captured in 60000 ms, killing.
DEBUG [launcher]: Process Chrome exited with code 0
DEBUG [temp-dir]: Cleaning temp dir C:\Users\Kunal\AppData\Local\Temp\karma-8656
3066
INFO [launcher]: Trying to start Chrome again (2/2).
DEBUG [launcher]: Restarting Chrome
DEBUG [temp-dir]: Creating temp dir at C:\Users\Kunal\AppData\Local\Temp\karma-8
6563066
DEBUG [launcher]: C:\Program Files (x86)\Google\Chrome\Application\chrome.exe --
user-data-dir=C:\Users\Kunal\AppData\Local\Temp\karma-86563066 --no-default-brow
ser-check --no-first-run --disable-default-apps --disable-popup-blocking --disab
le-translate http://localhost:9876/?id=86563066
DEBUG [web-server]: serving: E:\Projects\abb\Projects\WebApp\abb.web\nod
e_modules\karma\static/client.html
DEBUG [web-server]: serving: E:\Projects\abb\Projects\WebApp\abb.web\nod
e_modules\karma\static/karma.js
DEBUG [web-server]: upgrade /socket.io/1/websocket/rpgHU0_UF1MnvCwCWUuJ
DEBUG [karma]: A browser has connected on socket rpgHU0_UF1MnvCwCWUuJ
DEBUG [launcher]: Disconnecting all browsers
DEBUG [launcher]: Process Chrome exited with code 0
DEBUG [temp-dir]: Cleaning temp dir C:\Users\Kunal\AppData\Local\Temp\karma-8656
3066
wersje pakietu: wersja węzła: v0.10.28
"karma": "^0.12.16",
"karma-chrome-launcher": "^0.1.4",
"karma-jasmine": "^0.1.5",
plik konfiguracyjny:
// Karma configuration
// Generated on Sat May 24 2014 22:34:35 GMT+0530 (India Standard Time)
module.exports = function(config) {
config.set({
// base path that will be used to resolve all patterns (eg. files, exclude)
basePath: '',
// frameworks to use
// available frameworks: https://npmjs.org/browse/keyword/karma-adapter
frameworks: ['jasmine'],
// list of files/patterns to load in the browser
files: [
'app/js/vendor/angular.js',
'app/js/vendor/angular-route.js',
'test/lib/angular-mocks.js',
'app/js/app.debug.js',
'test/unit/**/*.spec.js'
],
// list of files to exclude
exclude: [
],
// preprocess matching files before serving them to the browser
// available preprocessors: https://npmjs.org/browse/keyword/karma-preprocessor
preprocessors: {
},
// test results reporter to use
// possible values: 'dots', 'progress'
// available reporters: https://npmjs.org/browse/keyword/karma-reporter
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_DEBUG,
// enable/disable watching file and executing tests whenever any file changes
autoWatch: false,
// start these browsers
// available browser launchers: https://npmjs.org/browse/keyword/karma-launcher
browsers: ['Chrome'],
// Continuous Integration mode
// if true, Karma captures browsers, runs the tests and exits
singleRun: false
});
};
Chrome otwiera się z localhost: // 9876 i pokazy "karma - począwszy od"
nie jest w stanie uczynić pracę karmy. Proszę pomóż.
Próbowałem ustawić autowatch: true i wyłączanie zapory, ale żaden z nich nie działał.
Czy kiedykolwiek znaleźć rozwiązanie tego problemu? Otrzymuję dokładnie tę samą wiadomość: 'Chrome nie przechwycił w 60000 ms, zabijając. –
Nie, przełączyłem się na PhantomJS. To działało w odniesieniu do moich testów. –
Tak, mam ten sam problem na naszym serwerze kompilacji. Myślałem, że było to spowodowane czymś w teamcity, ale mabey to tylko kwestia karma/chrom. – dss