-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Disconnected, because no message in 10000 ms. #1413
Comments
Jasmine doesn't launch a browser, it should be karma that's doing that for you. Check over here: https://github.com/karma-runner/karma Hope this helps. Thanks for using Jasmine! |
Hrmm ... I wonder why changing the Jasmine package version in isolation causes this behavior, but I shall follow up with the Karma team. Thanks, Gregg! |
Add this to your Karma.conf:
|
@byrondover I don't think the Karma team will be able to assist you much further on this issue. I was having the same problem and following the advice of @cport1 resolved my issue, but he set his timeout to nearly four minutes. I found that 30 seconds was more than enough time. Might bump it up to 60 seconds. Running this all on Jenkins daily so I'm sure I'll get an email if this happens again. For development I am running off of an older Macbook Pro 13" Mac OS X Sierra. |
Thanks, gents! Appreciate the advice. 🙂 |
Thanks @cport1 - This worked like a charm. |
The same issue is described here: jasmine/jasmine#1413
Using @swetapatil1 answer, I am now able to finally work! Using the flags from this:
I was finally able to forge a working karma.conf.json (for headless ubuntu+chrome): karma.conf.json
|
Jasmine 2.7.0 fails to launch headless Chrome (--no-sandbox) on Shippable node_js 7.4.0. As a workaround, reverting to 2.6.4 resolves the issue.
Logs copied below, for reference.
Please let me know if I can provide any further context or logs. 🙂 If you are already aware, please feel free to close this issue.
The text was updated successfully, but these errors were encountered: