Possible reasons for Selenium RemoteWebDriver command timeouts -
we have number of selenium tests running 24/7 , few times day getting random
webdriver timeout exception. example:
openqa.selenium.webdriverexception: http request remote webdriver server url http://*.*.*.*:4444/wd/hub/session/4957b6a8-c885-4dd7-98ab-373f35619495/url timed out after 120 seconds. ---> system.net.webexception: operation has timed out @ system.net.httpwebrequest.getresponse() @ openqa.selenium.remote.httpcommandexecutor.createresponse(webrequest request) --- end of inner exception stack trace --- @ openqa.selenium.remote.httpcommandexecutor.createresponse(webrequest request) @ openqa.selenium.remote.httpcommandexecutor.execute(command commandtoexecute) @ openqa.selenium.remote.remotewebdriver.execute(string drivercommandtoexecute, dictionary`2 parameters) @ openqa.selenium.remote.remotewebdriver.get_url() ...
usually happens in random places (when fetching current url, when clicking element, finding element, etc.) , in different tests.
remotewebdriver's command timeout http requests set 120s , none of timeouts set manage().timeouts().* exceed 60 seconds.
my question is, possible reasons command timeout?
it looks selenium or possibly chromedriver locks whatever reason. although unable verify visually since tests executed on headless machine.
could overlooked or misunderstood timeout setting?
versions: selenium v2.42.2, .net bindings v2.40.0, chromedriver 2.10
Comments
Post a Comment