Issue with chromedriver port when running with parallel

[uppak]

Hi

I am running tests parallel with this gem and so far all things are good and successfully able to incorporate in cloud environemnt also. But in some cases, our tests have quite and re-open browser. It is like @driver.quit which kills browser and chromedriver also and then browser is re-launched with new chrome session.

At this stage i don't have any chrome browser or chromedriver session running. So when relaunched with new driver session, sometimes it is starting on 9515 and sometimes on 9516.
9515 port is always opened and when it launches driver on 9515 there is no issue and test is passing successfully, but when driver session launched on 9516. It is saying unable to establish connection and tests are failing.

Not sure if parallel_tests taking ports randomly or chromedriver issues. Any help is appreciated? & is anyone faced this sort of issues?

i am using parallel_tests 2.27.1
chrome version 68(tried on 73 also)

[grosser]

not sure, most issues I heard about were capybara related ...
check wiki for port maybe https://github.com/grosser/parallel_tests/wiki#with-capybara040selenium----by-rgo ?

otherwise check if there is a way to set the port and add it to the wiki too ...
could maybe boot chrome and then test which port it is on somehow 🤷‍♂️

[grosser]

I'll close this since it's not a but in parallel-tests, please update if you find out anything though :)