-
Notifications
You must be signed in to change notification settings - Fork 19
Karma fails to kill SlimerJS #1
Comments
Can you give me the SlimerJS and Karma versions you are using ? Is it specific to a particular website or the problem happens on every website ? |
"grunt-karma": "~0.6.2",
"karma": "~0.10.9",
"karma-mocha": "~0.1.1",
"karma-slimerjs-launcher": "~0.1.2", |
What is the SlimerJS version (not the karma plugin), your OS, your SlimerJS install (XULRunner, Firefox + their version). |
Just tried your project with SlimerJS+XulRunner under Debian GNU/Linux without facing the issue: nfroidure@production:~/Bureau/Projects/request.js$ env "SLIMERJS_BIN=/home/nfrdure/Bureau/slimerjs-0.9.0/slimerjs" karma start --browsers=SlimerJS
INFO [karma]: Karma v0.10.9 server started at http://localhost:9876/
INFO [launcher]: Starting browser SlimerJS
INFO [Other 0.0.0 (Linux)]: Connected on socket Py0lNf5IQdrGnuX9lyey
Other 0.0.0 (Linux) request.js send object json FAILED
timeout of 10000ms exceeded
@/home/nfroidure/Bureau/Projects/request.js/node_modules/mocha/mocha.js:4241
Other 0.0.0 (Linux): Executed 1 of 5 (1 FAILED) ERROR (10.143 secs / 10.001 secs)
INFO [watcher]: Changed file "/home/nfroidure/Bureau/Projects/request.js/test/test.js".
Other 0.0.0 (Linux) request.js send object json FAILED
timeout of 10000ms exceeded
@/home/nfroidure/Bureau/Projects/request.js/node_modules/mocha/mocha.js:4241
Other 0.0.0 (Linux): Executed 1 of 5 (1 FAILED) ERROR (10.323 secs / 10 secs) |
I'm seeing this same issue. It is preventing me from running Slimer-based tests on Travis-CI. It's also a hassle locally since I have to manually close the XulRunner/Firefox window when the tests have completed. Locally I have: On Travis: It appears that a Gecko window is opened and it is prompting me to confirm navigation away from the page. The SIGKILL is sent by karma, but does not seem to actually do anything. |
Ok, so it looks like it is not a karma issue. Maybe you should submit the bug to the SlimerJS project. If there is a command line to avoid having any prompt, let me know, i'll add it to the slimerjs launch command line. Feel free to PR anyway if you find a workaround since at my level i'm unable to reproduce the bug. |
@nfroidure No prompt appears here so I think it's a different issue than @feltnerm' |
Here is what I get.
WARN [launcher]: SlimerJS was not killed in 2000 ms, sending SIGKILL.
And the process just hang on.
The text was updated successfully, but these errors were encountered: