-
-
Notifications
You must be signed in to change notification settings - Fork 8.6k
Description
What happened?
Everyday at specific timeframe my grid is going down, making to fail the all the pipelines. Grid is good on weekends as no pipelines are running against it.
I am really unsure why the grid is going down even though there are sufficient sessions avaialable. While running the pipeline the error shows "Cannot find session with id: 92598c7905b9a20bfcbe25414a79b6de Build info: version: '4.4.0', revision: 'e5c75ed026a' System info: host: 'xxxx', ip: 'x.x.x.x', os.name: 'Windows Server 2019', os.arch: 'amd64', os.version: '10.0', java.version: '11.0.16.1' Driver info: driver.version: unknown"
But once the pipeline completes the error is "OpenQA.Selenium.WebDriverException : The HTTP request to the remote WebDriver server for URL http://selenium-grid.unum.com:4444/wd/hub/session/2044c12416348b5c4f61ca618922146d/element timed out after 120 seconds"
I found these other bugs but those are on Docker
SeleniumHQ/docker-selenium#2135
#14322
How can we reproduce the issue?
This is happening at specific timeRelevant log output
2024-08-30T08:05:53.5372772Z Stack Trace:
2024-08-30T08:05:53.5372897Z at OpenQA.Selenium.Remote.HttpCommandExecutor.MakeHttpRequest(HttpRequestInfo requestInfo)
2024-08-30T08:05:53.5373067Z at OpenQA.Selenium.Remote.HttpCommandExecutor.Execute(Command commandToExecute)
2024-08-30T08:05:53.5373245Z at OpenQA.Selenium.Remote.RemoteWebDriver.Execute(String driverCommandToExecute, Dictionary`2 parameters)
2024-08-30T08:05:53.5373419Z at OpenQA.Selenium.Remote.RemoteWebDriver.FindElement(String mechanism, String value)Operating System
Windows server 2019 Datacenter
Selenium version
openjdk 11.0.16.1 2022-08-12 LTS
What are the browser(s) and version(s) where you see this issue?
Chrome 128.0.6613.85
What are the browser driver(s) and version(s) where you see this issue?
ChromeDriver.128.0.6613.84
Are you using Selenium Grid?
Selenium 4.152369