Chrome 93 request timed out for 60 seconds

[Lazaro Hernandez]

threw exception. OpenQA.Selenium.WebDriverException: The HTTP request to the remote WebDriver server for URL http://localhost:<port#>/session/87991d04de6064aed8060262bacb826f/element timed out after 60 seconds. 

Anyone seen this issue while using azure devops to run their automation tests? Tests run fine on local machine but when ran on a virtual machine via Azure Devops tests run fine 2/10 times

[Jasper van der Woude]

Yes! Experiencing this issue too tests running with Azure Devops on CI servers. Happening since chromedriver update to 93

Op vrijdag 10 september 2021 om 21:59:49 UTC+2 schreef lazuh...@gmail.com:

[Lazaro Hernandez]

after researching exactly how the webdriver/chromedriver/browser interacts, i saw that the default port number for chromedriver is 9515...all my failures are not using that port number. @jasper do you know of a way where we can print the port number that chromedriver is using? Some of my tests are passing so i want to see what port number theyre using. 

[Lazaro Hernandez]

I may have found a solution. I noticed that my tests always fails around ISearchContext.FindElement(). After further research, implicit wait is a big no no in selenium and so i turned it off. For me specifically, it would fail when the element didnt exist in the DOM. but the step was needed, because I needed to know if the element did not exist. So i will be updating the code to use .FindElements() instead of .FindElement().....

Further testing will be needed. 

[pgcl...@gmail.com]

Can you check https://groups.google.com/g/chromedriver-users/c/F6QoJkegYNc 

sounds like it might be the same issue?

[Robbie Hickey]

Our team is experiencing the same issue reported here when our tests are executed under TeamCity. Checked the linked discussion and we already have the `--disable-gpu` flag enabled.

[Lazaro Hernandez]

so far removing the implicit wait has fixed our issues.