-
Notifications
You must be signed in to change notification settings - Fork 311
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
SauceLabsTunnel Error: Failed to start Selenium listener #285
Comments
Also experiencing this issue with latest Sauce Labs Tunnel |
do you have anything listening on port 4444? i just had the same problem and fixed it by stopping my local selenium server. |
@neonstalwart nothing running on 4444 unfortunately.
I don't have selenium locally installed as well, if that helps. |
@zanona Try downgrading to 2.0.1, I bet it will work |
Hey guys, that persists even on 2.0.1, I have installed Thanks for your help. |
hey @zanona, did you ever find out what this issue was? I'm running intern-tutorial version 2.0.0 that uses intern version 2.1.1 and get the exact same thing above |
@d48 unfortunately I haven't found the issue. Since it was on my local machine and I was fine running tests remotely, which seemed to work without problems. |
thanks for the info @zanona. will post if I find anything |
Just to give context, when I initially ran
And then when re-running |
@zanona I had some error in my functional test syntax. copy and pasting what they had on Step 5 made the tests run fine locally so the issue was my typing. The error was masked because when re-running |
I'm still getting the "Failed to start Selenium listener" error too. |
Fixed it by killing the process on port 4444. |
@kmoe that's what I had to do as well as it attached to the port on the initial run and blocked it |
Hey guys, I am using the same configurations as in per the tutorial however, when trying to run test with my SauceLabs free OSS account locally and I get:
One interesting thing is that I am also using codeship.io to automate tests on push to github repo and from their server it seems to work fine.
Is there any specific configuration I should set locally (mac) to make it work?
Thanks
The text was updated successfully, but these errors were encountered: