search

ericmckean / chromedriver

Automatically exported from code.google.com/p/chromedriver
0 stars 0 forks source link

Chrome not reachable error. #1057

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
Run the below code in eclipse.

Code: 
public class Test1 {
    @Test
    public void EnggDotCom(){
    System.setProperty("webdriver.chrome.driver", "C:/Selenium Automation/OR/Executable_Files/chromedriver.exe");
    WebDriver driver = new ChromeDriver();
    driver.navigate().to("https://www.google.com");
    }
}

What is the expected output? What do you see instead?
chrome should launch the URL.

Selenium version: 2.45
chrome driver: 2.14
OS: win 8.1
Browser: Chrome
Browser version: v17

Error Log:

FAILED: EnggDotCom
org.openqa.selenium.WebDriverException: chrome not reachable
  (Driver info: chromedriver=2.14.313457 (3d645c400edf2e2c500566c9aa096063e707c9cf),platform=Windows NT 6.3 x86_64) (WARNING: The server did not provide any stacktrace information)
Command duration or timeout: 61.45 seconds
Build info: version: '2.45.0', revision: '5017cb8', time: '2015-02-26 23:59:50'
System info: host: 'BTG468741', ip: '172.23.169.172', os.name: 'Windows 8.1', 
os.arch: 'amd64', os.version: '6.3', java.version: '1.8.0_40'
Driver info: org.openqa.selenium.chrome.ChromeDriver
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
    at org.openqa.selenium.remote.ErrorHandler.createThrowable(ErrorHandler.java:204)
    at org.openqa.selenium.remote.ErrorHandler.throwIfResponseFailed(ErrorHandler.java:156)
    at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:599)
    at org.openqa.selenium.remote.RemoteWebDriver.startSession(RemoteWebDriver.java:240)
    at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:126)
    at org.openqa.selenium.remote.RemoteWebDriver.<init>(RemoteWebDriver.java:139)
    at org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:171)
    at org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:160)
    at org.openqa.selenium.chrome.ChromeDriver.<init>(ChromeDriver.java:117)
    at Engg.com_Automation.Test1.EnggDotCom(Test1.java:11)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:497)
    at org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84)
    at org.testng.internal.Invoker.invokeMethod(Invoker.java:714)
    at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901)
    at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231)
    at org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
    at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
    at org.testng.TestRunner.privateRun(TestRunner.java:767)
    at org.testng.TestRunner.run(TestRunner.java:617)
    at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
    at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
    at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
    at org.testng.SuiteRunner.run(SuiteRunner.java:240)
    at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
    at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
    at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224)
    at org.testng.TestNG.runSuitesLocally(TestNG.java:1149)
    at org.testng.TestNG.run(TestNG.java:1057)
    at org.testng.remote.RemoteTestNG.run(RemoteTestNG.java:111)
    at org.testng.remote.RemoteTestNG.initAndRun(RemoteTestNG.java:204)
    at org.testng.remote.RemoteTestNG.main(RemoteTestNG.java:175)

Original issue reported on code.google.com by ravikira...@gmail.com on 12 Mar 2015 at 5:52

GoogleCodeExporter commented 9 years ago 
in order to find chrome, it need to be in the system path.

Original comment by andrewch...@chromium.org on 12 Mar 2015 at 5:37

GoogleCodeExporter commented 9 years ago

Original comment by andrewch...@chromium.org on 12 Mar 2015 at 5:49

GoogleCodeExporter commented 9 years ago 
Yes Andrew, It is added.

Original comment by ravikira...@gmail.com on 13 Mar 2015 at 5:22

GoogleCodeExporter commented 9 years ago 
Are you seeing this all time or just occasionally? If I do a lot of runs, I see 
this error about 0.1% of the time (see issue 1058), so I'm wondering if you're 
seeing the same thing.

Original comment by samu...@chromium.org on 13 Mar 2015 at 10:52

GoogleCodeExporter commented 9 years ago 
Yes, I'm seeing this every time i run.

Original comment by ravikira...@gmail.com on 15 Mar 2015 at 5:41

GoogleCodeExporter commented 9 years ago 
OK. We're still trying to reproduce this on our end, but if there's any more 
information you can give about how you've got everything set up, it would help.

You mentioned that your browser version is "v17", but the current stable 
channel is at 41. What version of Chrome is reported when you browse to 
chrome://version?

Original comment by samu...@chromium.org on 16 Mar 2015 at 7:54

GoogleCodeExporter commented 9 years ago 
Actually, we have got a standalone installer of chrome version 17. We used this 
particular version.

Original comment by ravikira...@gmail.com on 17 Mar 2015 at 5:17

GoogleCodeExporter commented 9 years ago 
Is there any reason you need to test against Chrome 17? This is a very old 
release and is no longer supported by Google. In addition to security 
vulnerabilities, it's also not going to be very useful for testing against 
unless your users are also using the standalone installer.

Does the test work if you run it against Chrome 41?

Original comment by samu...@chromium.org on 17 Mar 2015 at 9:31

GoogleCodeExporter commented 9 years ago 
Yes, unfortunately our app is supported only by version 17 to chrome version 
35. So, Infact i'm actually trying to get the chrome version beyond 32, still 
couldn't find it.

Yes, the test works well with chrome v41, but as i said our app shows limited 
support to the new chrome version 41.

Original comment by ravikira...@gmail.com on 18 Mar 2015 at 5:35

GoogleCodeExporter commented 9 years ago 
Sorry, we're not able to support obsolete versions of Chrome.

An old version of ChromeDriver might work, but you'll be running with many 
known security vulnerabilities in both the driver as well as the browser, so I 
wouldn't recommend it. We're also not able to provide support for old 
ChromeDriver releases, unless the bug still exists in the current release.

Original comment by samu...@chromium.org on 19 Mar 2015 at 10:48