-
-
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 4.15 with C# - Exception in Parallel Test Execution "OpenQA.Selenium.NoSuchDriverException : Unable to obtain chrome using Selenium Manager" #13342
Comments
@dcdraper, 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! |
4.16.0 is out since a couple of weeks. Can you please check that version? |
We're trying to release when Google releases chrome, so we're shooting for - https://chromiumdash.appspot.com/schedule You can try to use nightly, the last built should work... Hmm, looks like I messed up the nightly build with one of the recent changes, though, I guess I need to figure that out. |
And I just noticed this is C# not Java, so no nightly. Also, I think this may be related to #12425 ? |
You aren't alone. We started experiencing similar, if not the same issue as of stable version 4.16.1. We tried 4.16.2 as well and the issue is not resolved. We rolled back to 4.15.0 and all is well. Essentially, we have a .NET project (C#) which runs tests via Azure DevOps CI/CD in parallel across multiple agents. Have been using Selenium for some time and this is seemingly our first trouble. 4.15.0 - Example of log output from initial SmokeTest run via DevOps agent:
4.16.2 - Example of log output from initial SmokeTest run via DevOps agent - immediate failures, no tests run:
We might try and see if the workaround mentioned |
Heads up - we have upgraded and tested |
Excellent. I'll close this, then. We can re-open if we determine this bug is still present |
@titusfortner
|
We have several similar issues open in multiple languages. We should review our overall strategy. |
I think these have been addressed. I'm closing this. |
@titusfortner which version addresses this? |
I updated to 4.18.1 and I am still seeing errors: INFO Bold: Ending test.. ERROR: OpenQA.Selenium.NoSuchDriverException : Unable to obtain chrome using Selenium Manager; For documentation on this error, please visit: https://www.selenium.dev/documentation/webdriver/troubleshooting/errors/driver_location |
This issue has been automatically locked since there has not been any recent activity since it was closed. Please open a new issue for related bugs. |
What happened?
The failures are intermittent and do not happen in each run.
The tests fail with selenium-manager.exe exception "Unable to obtain chrome using Selenium Manager" and error message "The process cannot access the file because it is being used by another process. (os error 32)"
We are using a .runsettings file and setting NumberOfTestWorkers to 8. Only about three tests fail at the beginning of each run. It seems that once chrome is installed by one of the early tests/threads that the issue no longer presents.
Version 4.15 is the first and only version we have tried using to manage chrome and chromedriver.
As a workaround we are running the command "selenium-manager.exe --browser chrome --debug" on the test agent in the pipeline after building the solution and before the tests start running.
How can we reproduce the issue?
Relevant log output
Operating System
Windows 10
Selenium version
Selenium 4.15, C#
What are the browser(s) and version(s) where you see this issue?
Chrome Version 120.0.6099.109 (Official Build) (64-bit)
What are the browser driver(s) and version(s) where you see this issue?
chromedriver.exe x64 version 120.0.6099.71
Are you using Selenium Grid?
no
The text was updated successfully, but these errors were encountered: