[🚀 Feature]: The ability to change the client timeout of Selenium Grid to more than 3 minutes

[tking16]

Feature and motivation

My test setup requires more time to get started as it involves multiple iOS Simulators (at least four), but the tests will timeout due it's 3 minute default as stated here this is currently non-configurable but would be great to be able to make this timeout longer.

Usage example

To actually reproduce the issue it's best to start testing with no emulators currently running. Create 4-6 appium.yaml files and the same amount of node.toml files and use pytest-xdist to setup parallel testing within Selenium Grid.

After a while You should see the error:

E       selenium.common.exceptions.SessionNotCreatedException: Message: Could not start a new session. java.net.http.HttpTimeoutException: request timed out

[github-actions]

@tking16, thank you for creating this issue. We will troubleshoot it as soon as we can.

---

Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

[diemol]

That is the timeout this client should use.

The ideal solution would be to add the configured session-timeout from the Node to the NodeStatus and use that one when the RemoteNode object is created.

[github-actions]

This issue is looking for contributors.

Please comment below or reach out to us through our IRC/Slack/Matrix channels if you are interested.