Random NoHttpResponseException thrown using ChromeDriver in selenium

Google did an update for Chrome over the weekend, and I'm trying to run some automated tests using Selenium. Since the update, every 5 or 6 starts leads to the following error. I run the test again and it works great. It is just very annoying because it is interrupted randomly.

org.openqa.selenium.WebDriverException: org.apache.http.NoHttpResponseException: The target server failed to respond Build info: version: '2.6.0', revision: '13840', time: '2011-09-13 16:51:41' System info: os.name: 'Windows 7', os.arch: 'amd64', os.version: '6.1', java.version: '1.6.0_26' Driver info: driver.version: RemoteWebDriver at org.openqa.selenium.chrome.ChromeCommandExecutor.execute(ChromeCommandExecutor.java:59) at org.openqa.selenium.remote.RemoteWebDriver.execute(RemoteWebDriver.java:377) at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:182) at org.openqa.selenium.remote.RemoteWebDriver.findElementById(RemoteWebDriver.java:199) at org.openqa.selenium.By$ById.findElement(By.java:210) at org.openqa.selenium.remote.RemoteWebDriver.findElement(RemoteWebDriver.java:174) at com.core.FindElementAndWait.apply(FindElementAndWait.java:28) at com.core.FindElementAndWait.apply(FindElementAndWait.java:1) at org.openqa.selenium.support.ui.FluentWait.until(FluentWait.java:173) ... 68 more 
+4
source share
2 answers

I have a fix for this error, but it has not yet been released. There is a workaround there https://code.google.com/p/selenium/issues/detail?id=2513 , and if you track this problem, you will be notified of the progress of the correction.

+2
source

We saw the same issue with ChromeDriver. The solution in our case was to add Thread.sleep(1) between each call to the selenium RC interface.

For some reason, he solved the problem.

0
source

All Articles