-
-
Notifications
You must be signed in to change notification settings - Fork 8.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[🐛 Bug]: Timeout set to 16 minutes, but always fails with timeout after 9 minutes #14446
Comments
@codex70, thank you for creating this issue. We will troubleshoot it as soon as we can. Info for maintainersTriage this issue by using labels.
If information is missing, add a helpful comment and then
If the issue is a question, add the
If the issue is valid but there is no time to troubleshoot it, consider adding the
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable
After troubleshooting the issue, please add the Thank you! |
Why are you not setting any timeout on the Grid? |
Because I wasn't aware that was an option, I must have missed that. Will try that now |
OK, I've tried with the following options in the docker compose file, but it hasn't made any difference:
Are there any other settings for the chrome node container, or anything else that I might be missing? |
|
Thank you, the example I found must have been out of date. I have now put:
However this still makes no difference. One thing I did notice was that in the error message I get the following details from the driver, which do not appear to relate to any of the timeouts I have set:
Are there any other settings that I'm missing or have misunderstood? |
If I set the following options, they get passed through to selenium, but it still makes no difference:
Whatever settings I change, I still end up with the following errors in the selenium hub docker container:
It still consistently fails at 9 minutes, then takes a further 9 minutes to close and stop the driver. |
As a follow up, if I run with standalone chrome instead of going through selenium hub, the above code works as expected and there are no timeouts. It doesn't really solve the problem, but for me, for the time being, this is a work around I can live with. @diemol, thank you for all your help, I'm not sure if you want me to close this issue, or leave it open? |
What happened?
This is similar to the problem at #9314. I am trying to test a report which takes around 12 minutes to run. I am using selenium hub in docker with google browser. The tests are run using TestNG and Cucumber.
Originally I was seeing the same 3 minute timeout as described in the other issue, but I've implemented the code shown in the page, and now see a different timeout issue after 9 minutes (it is always exactly 9 minutes). The timeout also seems to block the driver from quitting and stopping for a significant amount of time (around a further 13 minutes). After this, I need to restart the docker container in order to connect again to the remote web driver.
How can we reproduce the issue?
Relevant log output
Operating System
Windows 11 and Docker
Selenium version
Java 4.23.1
What are the browser(s) and version(s) where you see this issue?
Chrome Remote
What are the browser driver(s) and version(s) where you see this issue?
Chrome Browser version 127.0.6533.99
Are you using Selenium Grid?
Grid version: 4.23.1
The text was updated successfully, but these errors were encountered: