-
-
Notifications
You must be signed in to change notification settings - Fork 8.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[🐛 Bug]: 4.12.0 Selenium Grid stopped working (PersistentCapabilities cannot be cast to class MutableCapabilities) #12663
Comments
@eugenedani, thank you for creating this issue. We will troubleshoot it as soon as we can. Info for maintainersTriage this issue by using labels.
If information is missing, add a helpful comment and then
If the issue is a question, add the
If the issue is valid but there is no time to troubleshoot it, consider adding the
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable
After troubleshooting the issue, please add the Thank you! |
This is a known issue. We'll be releasing Selenium 4.12.1 for Java soon. |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
What happened?
We use Hub and Node to run Selenium tests, after updating to v. 4.12.0 Selenium Grid stopped working because of error class org.openqa.selenium.PersistentCapabilities cannot be cast to class org.openqa.selenium.MutableCapabilities (org.openqa.selenium.PersistentCapabilities and org.openqa.selenium.MutableCapabilities are in unnamed module of loader org.openqa.selenium.grid.Bootstrap$PossessiveClassLoader @29453f44)
Is MutableCapabilities class was deprecated and we should use PersistentCapabilities class?
How can we reproduce the issue?
Relevant log output
Operating System
ubuntu:jammy-20230624
Selenium version
4.12.0
What are the browser(s) and version(s) where you see this issue?
any
What are the browser driver(s) and version(s) where you see this issue?
any
Are you using Selenium Grid?
4.12.0
The text was updated successfully, but these errors were encountered: