Closed benzman81 closed 7 years ago
@benzman81 according to this documentation section you can adjust several timeout values:
-service-startup-timeout 30s
- Docker container or driver process startup timeout-session-attempt-timeout 30s
- New session attempt timeout, i.e. POST /wd/hub/session
HTTP request timeout.-session-delete-timeout 10s
- Session removal HTTP request timeout-timeout 60s
- Session idle timeout, i.e. time between separate HTTP requests to Selenium API which automatically causes session to be closed.You can obtain the same documentation via $ selenoid -help
command.
sorry about this issue. I already set "-timeout xxx" but I didnt push to remote :-D
Hello @vania-pooh, my docker-compose.yml file looks like this : `services: selenoid: image: "aerokube/selenoid:latest-release" container_name: hub networks:
And pom.xml has forkcount set to 25
But I see max 16 sessions are executing in parallel,don't know why. But, If I remove
-timeout`, everything working fine, it's starting 25 sessions in parallel. Am I missing something?
@Programmer-Admin you have to check Selenoid logs and your test code logs to get an idea of the number of browser sessions being started. Trying to check the same in Selenoid UI is not a guarantee of showing correct number, because in Selenoid UI everything is refreshed every 5 seconds and short test cases can be executed faster.
Hi,
moving from "selenium grid + grid extras" to "ggr + selenoid" I get a lot of "Session timed out or not found" errors like these:
Do you have any idea? Can I increase the timeout some how to not run into it?
Regards, Markus