search

jitsi / jitsi-meet-torture

Apache License 2.0
161 stars 149 forks source link

Selenium Grid - participant n is not connected #477

Closed VitalyVaryvdin closed 1 year ago

VitalyVaryvdin commented 2 years ago

Running malleus.sh on my (properly set up) Selenium Grid results in following execution:

[24] Start testMain.
[23] Start testMain.
[25] Start testMain.
[22] Start testMain.
[26] Start testMain.
[30] No participant type specified for prefix: web.participant1, will use Chrome...
[29] No participant type specified for prefix: web.participant1, will use Chrome...
[27] No participant type specified for prefix: web.participant1, will use Chrome...
[28] No participant type specified for prefix: web.participant1, will use Chrome...
[31] No participant type specified for prefix: web.participant1, will use Chrome...
[pool-3-thread-1] INFO io.github.bonigarcia.wdm.WebDriverManager - Using chromedriver 97.0.4692.71 (resolved driver for Chrome 97)
[pool-5-thread-1] INFO io.github.bonigarcia.wdm.WebDriverManager - Using chromedriver 97.0.4692.71 (resolved driver for Chrome 97)
[pool-4-thread-1] INFO io.github.bonigarcia.wdm.WebDriverManager - Using chromedriver 97.0.4692.71 (resolved driver for Chrome 97)
[pool-2-thread-1] INFO io.github.bonigarcia.wdm.WebDriverManager - Using chromedriver 97.0.4692.71 (resolved driver for Chrome 97)
[pool-1-thread-1] INFO io.github.bonigarcia.wdm.WebDriverManager - Using chromedriver 97.0.4692.71 (resolved driver for Chrome 97)
[pool-2-thread-1] INFO io.github.bonigarcia.wdm.WebDriverManager - Exporting webdriver.chrome.driver as C:\Users\Vitaly\.cache\selenium\chromedriver\win32\97.0.4692.71\chromedriver.exe
[pool-5-thread-1] INFO io.github.bonigarcia.wdm.WebDriverManager - Exporting webdriver.chrome.driver as C:\Users\Vitaly\.cache\selenium\chromedriver\win32\97.0.4692.71\chromedriver.exe
[pool-4-thread-1] INFO io.github.bonigarcia.wdm.WebDriverManager - Exporting webdriver.chrome.driver as C:\Users\Vitaly\.cache\selenium\chromedriver\win32\97.0.4692.71\chromedriver.exe
[pool-3-thread-1] INFO io.github.bonigarcia.wdm.WebDriverManager - Exporting webdriver.chrome.driver as C:\Users\Vitaly\.cache\selenium\chromedriver\win32\97.0.4692.71\chromedriver.exe
[pool-1-thread-1] INFO io.github.bonigarcia.wdm.WebDriverManager - Exporting webdriver.chrome.driver as C:\Users\Vitaly\.cache\selenium\chromedriver\win32\97.0.4692.71\chromedriver.exe
[38] Participant 0 is NOT connected.
[40] Participant 0 is NOT connected.
[39] Participant 0 is NOT connected.
[41] Participant 0 is NOT connected.
[37] Participant 0 is NOT connected.

After that execution is just paused and nothing happens.

Cmd: /scripts/malleus.sh --conferences=5 --participants=1 --senders=1 --audio-senders=1 --senders-per-node=1 --receivers-per-node=1 --duration=60 --join-delay=60 --room-name-prefix=TestRoom --hub-url="http://localhost:4444/wd/hub" --instance-url="" --use-node-types=false --use-load-test=false --max-disrupted-bridges-pct=100 --headless

Upd: removing max-disrupted-bridges-pct results in different error which says Could not start a new session. Could not start a new session. Error while creating session with the driver service. Stopping driver service: Could not start a new session. Response code 500. Message: unknown error: Chrome failed to start: crashed. (unknown error: DevToolsActivePort file doesn't exist)

VitalyVaryvdin commented 2 years ago

Looks like Chrome and driver version mismatch. Tests are downloading driver for v97, but selenium node is v96