Pavel Zilke

> [HandlersIT.copyVariable(Browser)[2]] java.lang.RuntimeException: Failed to create driver > at core.BaseTest.initDriver(BaseTest.java:107) > at BaseComponentIT.openBrowserAndLogin(BaseComponentIT.java:78) > at BaseComponentIT.openBrowserAndStartProcess(BaseComponentIT.java:83) > at HandlersIT.copyVariable(HandlersIT.java:32) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) >...

browsers.json: ``` { "firefox": { "default": "94.0", "versions": { "94.0": { "image": "selenoid/firefox:94.0", "port": "4444", "path": "/wd/hub", "tmpfs": { "/tmp": "size=512m" } } } }, "chrome": { "default": "98.0", "versions":...

I have a question why selenoid ignores parameter -session-attempt-timeout ? I run it with a parameter **-session-attempt-timeout 60s** or **-session-attempt-timeout 1m** But in the log: 2022-04-14T23:09:39.067596885Z 2022/04/14 23:09:39 [0] [SESSION_ATTEMPT_TIMED_OUT]...

I see such messages in files like selenoid0b2a3b67dd4565514c471a15a7c2e0ae.log from the directory /opt/selenoid/logs in selenoid docker-container

Thanks. In most cases, the tests work fine, but sometimes this happens. The reason has not yet been understood. Any suggestions why this might happen?

Moved the launch of tests to a less loaded server. But today I got this error: 2022-04-21T00:08:49.073818143Z 1650499729072 Marionette FATAL Remote protocol server failed to start: Error: Could not bind...

helm-chart is not supported anymore?