-
-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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]: Selenium Manager sometimes fails in parallel test run #11620
Comments
@attila-fazekas, 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! |
Looks like a permission denied error. This is intermittent? I wonder if we implemented #11359 instead of extracting to separate temporary directories if that might fix it? |
@attila-fazekas Thanks a lot for reporting. I have confirmed this problem using the provided parallel test. The underlying cause is the following:
@titusfortner Yes, maybe extracting to a separate folder (like I discussed the benefits of having the Selenium Manager binary in the cache in #11517. To do that, I think there are two alternatives:
I suppose some decision about it needs to be taken (in a TLC meeting?). |
We already discussed caching the manager at a previous TLC meeting; we don't need to implement the mini-manager to support just the caching. Though, thinking through this, we might need to implement retry functionality in the bindings, because two threads calling the binary at the same time is still going to have this issue. This is probably a bindings fix and not a rust fix? |
Yes, it seems it is an issue on the side of the binding (Java, in this case). |
I found an easy fix for this, see PR #11640. |
What happened?
Have noticed that sometimes Selenium Manager fails to configure driver executable path if tests are run in parallel.
Environment:
Java: Oracle OpenJDK 17.0.2
Gradle: 7.4
Was able to reproduce it both with jUnit and TestNG, please see the code in the repository below.
Before running tests, make sure neither specific driver locations provided, nor PATH environment variable set for drivers.
Run the tests until you
get java.lang.IllegalStateException: The path to the driver executable...
exception.How can we reproduce the issue?
Relevant log output
Operating System
macOS Mojave
Selenium version
Java 4.8
What are the browser(s) and version(s) where you see this issue?
Chrome 109.0.5414.119, Firefox 108.0.1, Edge 109.0.1518.70
What are the browser driver(s) and version(s) where you see this issue?
ChromeDriver 109.0.5414.74, GeckoDriver 0.32.0, EdgeDriver 109.0.1518.70
Are you using Selenium Grid?
No
The text was updated successfully, but these errors were encountered: