-
Notifications
You must be signed in to change notification settings - Fork 228
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
Error: ChromeDriver did not start within 5000ms #144
Comments
I'm having the same issue but on a Docker container running node:6.
Maybe relevant I'm running my tests without building the app. Like: new Application({
path: path.resolve(__dirname, '../node_modules/.bin/electron'),
args: [path.resolve(__dirname, '../')],
});
|
Same issue... 'ChromeDriver did not start within 5000ms' |
I could get ChromeDriver working by adding a proxy exception in my terminal.
|
Sadly that did not solve the issue for me. @armoucar how is that related? Maybe I can try out some other things related to it. |
At work I have to have proxies configuration on my terminal and I think ChromeDriver is a server running locally... When at home, with all proxies deactivated, I tested the same project I was trying to run the tests and it worked normally. I could then assume it was a proxy problem, in my case. |
@devwithin @armoucar Is the application not starting at all when running the tests? I have a demo repo if you want to reference that to see if it works for you. |
In my environment you demo works fine, as long as I set my |
@jwood803 your demo doesn't work for me but it seems to be an issue in the test file: |
@armoucar Thanks a lot. Your solution worked for me.
Turns out this was a problem with proxy setting. |
@Siilwyn Interesting! I haven't seen that error locally. Simple fix, though :) |
Can this be re-opened please? I'm still struggling with the same problem. Or should I open a new issue? |
@Siilwyn I'll reopen this issue as your problem looks very similar to mine. I suspect that this might be because of some network or proxy config problem. |
@devwithin thank you! |
That is weird, indeed. I've never even needed to use that in any of my tests. |
Alright I solved it on my end by installing display server related packages that are needed for chrome driver to run.
Think I'm going to find and try a docker image that already has the required chrome driver dependencies. |
@Siilwyn could you please tell me why it's failing - logs - https://travis-ci.org/zulip/zulip-electron/jobs/189773598 |
@akashnimare your error is not related to the issue described above. And sorry I don't know why it's failing. |
I'm experiencing the same error as Siilwyn, but when I try to install the packages he mentions I get errors that such packages do not exist. I am using the |
I ended up using a different docker image which was already setup for doing headless electron testing: |
I had a similar problem, after switching from mocha to ava. Reinstalling all yarn install --force |
In my case (spectron 5.0.0) solution was to run |
this helped me! thanks! |
I just removed that runner and started fresh one. New Runner downloaded Spectron and ChromeDriver on start and Chrome worked. |
I'm trying to run the getting started script from here (slightly modified).
I've tried to run this script but I'm getting following error
I'm on osx 10.11 with
The text was updated successfully, but these errors were encountered: