-
-
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]: Fails to start a new session using Chrome #2462
Comments
@rohithkk, 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! |
What are the capabilities set in your tests? Is managed downloads enabled in test and also |
@VietND96 I do not have any custom desired capabilities set. I have posted the code snippet for starting a new chrome driver session. The stacktrace also shows all the "capabilities" that are being requested.
|
In logs, that is browser options. Did you set any other caps that have prefix |
@VietND96 the only |
Env var |
I have removed that variable but it didn't help. Still running into same issue |
What happened?
We have automation tests using Selenium framework that run on Docker container during CI/CD process. We have dependency on
org.seleniumhq.selenium:selenium-java:4.15.0
and use the Devtools API to capture network trace and request/responses. We are using classes fromorg.openqa.selenium.devtools.v117.*
package.This logic works perfectly fine when running the tests on docker container with the image
selenium/standalone-chrome:117.0-20231004
.I'm trying to update the selenium and docker image version. I chose the latest available version selenium library
org.seleniumhq.selenium:selenium-java:4.26.0
and the docker image asselenium/standalone-chrome:130.0-20241101
. But this time, the tests fail to run since the Chrome session cannot be created. Code for creating webdriver instance is straightforward.Relevant log output
Operating System
Kubernetes
Docker Selenium version (image tag)
selenium/standalone-chrome:130.0-20241101
Selenium Grid chart version (chart version)
No response
The text was updated successfully, but these errors were encountered: