Closed diemol closed 6 years ago
Fixed by 7055d6f64c29368092bcb07d606d9605b7ec6247 Version 3.8.1 released with this fix.
Just tested it and it works well. Thanks @barancev
Thanks @barancev
@barancev - I can't find the 3.8.1 release of selenium-server-standalone. Did this not get deployed?
Thanks, @lmtierney ! I'd forgotten that release hierarchy was available. I was expecting that Maven would be able to download the artifact automatically, but it hasn't been released to the public Maven repos.
Version 3.8.1 is available in maven central: http://search.maven.org/#artifactdetails%7Corg.seleniumhq.selenium%7Cselenium-java%7C3.8.1%7Cjar
But, yes, selenium server standalone is not a maven artifact.
Meta -
OS: OSX 10.12.6 Selenium Version: 3.8.0 (Java and Python bindings, also Grid) Browser: Chrome
Browser Version:
62.0.3202.94 ChromeDriver=2.33.506106
Expected Behavior -
Start new session when running a test agains a Grid
Actual Behavior -
No session is created and this the error at the client side
Steps to reproduce -
These are the hub and node logs:
hub:
node:
I think the issue could be here:
Seems that the Chrome options are receiving a null as value for the binary key.
EDIT: I tried again with the grid in Standalone mode, and it works. Seems that it only fails when using hub/node.