Moving from 3.0.0-beta2 to 3.0.1 breaks ability to run tests in parallel.

[bradley8]

Meta -

OS: Windows 7 Enterprise 64-bit
Selenium Version: 3.0.1
Browser: Chrome
Browser Version: 54.0.2840.71 m

Expected Behavior - Ability to run tests in parallel as I have in the past using versions up to and including Selenium version 3.0.0 beta2

Actual Behavior - Unable to run tests in parallel. I can point our test suite at an instance of Grid 3.0.0-beta-2 and tests run in parallel without issue, when I point the exact same test suite to Grid 3.0.1 the tests run one at a time and not in parallel as expected. The configuration is exactly the same for both Grids and both Grids show 10 Chrome instances available as confirmed in the Grid Console. I'm using MSTest which I've been using with Grid for years without issue.

Steps to reproduce -

----Start a Grid using Selenium 3.0.0-beta2 ----
java -jar selenium-server-standalone-3.0.0-beta2.jar -role hub -port 4444
java -jar selenium-server-standalone-3.0.0-beta2.jar -role node -hub http://localhost:4444/grid/register -browser "browserName=chrome,version=ANY,maxInstances=10,platform=WINDOWS"

---Start another grid using Selenium 3.0.1 ---
ava -jar selenium-server-standalone-3.0.1 -role hub -port 4445
java -jar selenium-server-standalone-3.0.1 -role node -hub http://localhost:4445/grid/register -browser "browserName=chrome,version=ANY,maxInstances=10,platform=WINDOWS"

---Point tests to Grid 3.0.0-beta2 and tests run in parallel---
var hubUri = new Uri("http://localhost:4444/wd/hub");

---Point exact same test suite to Grid 3.0.1 and tests do not run in parallel. They run, but they only run one at a time, not in parallel---
var hubUri = new Uri("http://localhost:4445/wd/hub");

[lukeis]

you haven't provided enough information here for us to troubleshoot what issue you may be having.

Please provide reproducible steps or ask questions on the selenium-users google group -
https://groups.google.com/forum/#!forum/selenium-users

When you provide reproducible steps we can reopen the issue

[bradley8]

Sorry, I had the steps to reproduce in the post but they were inside of "<!-- -->".
Palm to Forehead! Steps to reproduce are in there now, thanks!

[lukeis]

can confirm something is quite wrong right now...

@mach6 !! :)

[mach6]

I have not ran into this but will certainly check.

what version of chromedriver?

[mach6]

Nevermind, re: chromedriver.

Confirmed. This is a registration bug. It will be fixed soon.

[bradley8]

Awesome, thank you!

[lukeis]

there's a workaround if on the node you specify -maxSession 10 it will work

[bradley8]

excellent, trying that now... Update: Workaround works great, thanks!