You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have the following setup:
OS: Windows Server 2012
Selenium: version 2.47.1 node running as a windows service (logged in as a user account with admin rights)
OperaChromiumDriver: 0.2.2 (it says 0.2.0 in the logs, but I am sure I downloaded version 0.2.2 from the releases tab)
Opera: 31.0 stable release
The linked chromedriver issue has a project member saying that it is an issue in chromedriver, and that Chromedriver 2.17 should be working, however as explained in my comment (#45) on the issue for me Chromedriver 2.16 works fine as long as I update to Chrome 45 beta.
I resolved my issue with Opera as well by upgrading to Opera 32 beta. I have posted this here mainly as a service for other people having the same issue. If it is indeed an issue in Chromium the issue should resolve itself as soon as Chrome 45 and Opera 32 are released as stable releases.
The text was updated successfully, but these errors were encountered:
I get the following error:
The HTTP request to the remote WebDriver server for URL http://xxx:yyy/wd/hub/session timed out after 60 seconds. OpenQA.Selenium.WebDriverException
It seems to be related to Chromium since Chrome has the same issue. As seen here: https://code.google.com/p/chromedriver/issues/detail?id=1080
I have the following setup:
OS: Windows Server 2012
Selenium: version 2.47.1 node running as a windows service (logged in as a user account with admin rights)
OperaChromiumDriver: 0.2.2 (it says 0.2.0 in the logs, but I am sure I downloaded version 0.2.2 from the releases tab)
Opera: 31.0 stable release
The linked chromedriver issue has a project member saying that it is an issue in chromedriver, and that Chromedriver 2.17 should be working, however as explained in my comment (#45) on the issue for me Chromedriver 2.16 works fine as long as I update to Chrome 45 beta.
I resolved my issue with Opera as well by upgrading to Opera 32 beta. I have posted this here mainly as a service for other people having the same issue. If it is indeed an issue in Chromium the issue should resolve itself as soon as Chrome 45 and Opera 32 are released as stable releases.
The text was updated successfully, but these errors were encountered: