-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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]: cannot find msedge binary selenium/node-edge:4.11.0-20230801 #1910
Comments
@amardeep2006, 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! |
Our CI tests are passing with 4.11.0, so I need a complete reproducible test case to triage this. |
@diemol Let me prepare a small script and share. Here are the container logs in the meanwhile.
|
@diemol I found the scenario when this is happening. This is happening with non trusted ssl certificates and wdio framework combination. Workaround : I had to use --ignore-certificate-errors in wdio config under capabilities
Note : This behavior is specific to MSEdge only where browser is not even launched. With Google Chrome, browser is at least launched . |
This is very strange, as the message comes directly from MSEdgeDriver. Could you please report it to them? |
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?
Tests are breaking against selenium/node-edge:4.11.0-20230801 docker image.
The ms edge is failing to start with error
cannot find msedge binary
The same tests are passing against selenium/node-chrome:4.11.0-20230801
Command used to start Selenium Grid with Docker
Relevant log output
Operating System
Windows10 WSL2
Docker Selenium version (tag)
4.11.0-20230801
The text was updated successfully, but these errors were encountered: