karma-junit-reporter: Cannot read property '33038646' of null - karma-junit-reporter/index.js:93:22

reproduced here https://github.com/el-net/bs_karma_eval

when run locally as:

karma start karma/lc.js

reproduction is inconsistent 😦

full error:


Missing error handler on `socket`.
TypeError: Cannot read property '30193015' of null
    at specSuccess.specSkipped.specFailure (/Users/osher/ws/POC/bs_karma_eval/node_modules/karma-junit-reporter/index.js:93:22)
    at onSpecComplete (/Users/osher/ws/POC/bs_karma_eval/node_modules/karma/lib/reporters/base.js:78:12)
    at null.<anonymous> (/Users/osher/ws/POC/bs_karma_eval/node_modules/karma/lib/events.js:13:22)
    at emit (events.js:129:20)
    at onResult (/Users/osher/ws/POC/bs_karma_eval/node_modules/karma/lib/browser.js:216:13)
    at Socket.<anonymous> (/Users/osher/ws/POC/bs_karma_eval/node_modules/karma/lib/events.js:13:22)
    at Socket.emit (events.js:129:20)
    at Socket.onevent (/Users/osher/ws/POC/bs_karma_eval/node_modules/karma/node_modules/socket.io/lib/socket.js:330:8)
    at Socket.onpacket (/Users/osher/ws/POC/bs_karma_eval/node_modules/karma/node_modules/socket.io/lib/socket.js:290:12)
    at Client.ondecoded (/Users/osher/ws/POC/bs_karma_eval/node_modules/karma/node_modules/socket.io/lib/client.js:193:14)
    at Decoder.Emitter.emit (/Users/osher/ws/POC/bs_karma_eval/node_modules/karma/node_modules/socket.io/node_modules/socket.io-parser/node_modules/component-emitter/index.js:134:20)
    at Decoder.add (/Users/osher/ws/POC/bs_karma_eval/node_modules/karma/node_modules/socket.io/node_modules/socket.io-parser/index.js:247:12)
    at Client.ondata (/Users/osher/ws/POC/bs_karma_eval/node_modules/karma/node_modules/socket.io/lib/client.js:175:18)
    at Socket.emit (events.js:107:17)
    at Socket.onPacket (/Users/osher/ws/POC/bs_karma_eval/node_modules/karma/node_modules/socket.io/node_modules/engine.io/lib/socket.js:99:14)
    at WebSocket.emit (events.js:129:20)

About this issue

Original URL
State: closed
Created 9 years ago
Reactions: 15
Comments: 35 (10 by maintainers)

Commits related to this issue

fix (runner): ignore browser_complete event emitted after run_complete event Closes #61 — committed to dschaller/karma-junit-reporter by deleted user 8 years ago
fix (runner): ignore browser_complete event emitted after run_complete event Closes #61 — committed to dschaller/karma-junit-reporter by deleted user 8 years ago
Defend against run events firing in the wrong order. See https://github.com/karma-runner/karma-junit-reporter/issues/61#issuecomment-264468229 as for why. What this mainly does is expose the real pr... — committed to randakar/karma-junit-reporter by randakar 8 years ago
Initialize var suites early As https://github.com/karma-runner/karma-junit-reporter/issues/61#issuecomment-264468229 Minor cleanup. Doing it this way should be faster though (no constructor call over... — committed to randakar/karma-junit-reporter by randakar 8 years ago
fix: initialize var suites early As https://github.com/karma-runner/karma-junit-reporter/issues/61#issuecomment-264468229 Minor cleanup. Doing it this way should be faster though (no constructor ca... — committed to karma-runner/karma-junit-reporter by randakar 8 years ago
fix: release memory held by a testsuite after we're done with it. As https://github.com/karma-runner/karma-junit-reporter/issues/61#issuecomment-264468229 Minor cleanup. Doing it this way should be ... — committed to karma-runner/karma-junit-reporter by randakar 8 years ago

Most upvoted comments

As I’ve mentioned before: lots of modules have this problem. “var suites” got copied all over the place. I bet the coverage reporter has it’s own incarnation of it.

randakar on Apr 5, 2017