-
-
Notifications
You must be signed in to change notification settings - Fork 8k
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
Selenium fails to launch when running on a single cpu #6605
Comments
I can confirm the issue in my Windows VM also running on a single core... |
I can confirm this issue is occurring on CentOS with a single core. |
Same issue is occurring when I try to run it in the docker container that has single CPU |
@AndrewFinlay @adrianer @Twb3 @milindm24 |
it happens for both |
@milindm24 could you please post the command used to start the docker container? |
This is happening for me as well, in Gitlab's CI. Unfortunately, I don't have many details since they abstract out a lot. I opened a support ticket here: https://forum.gitlab.com/t/insufficient-configured-threads-selenium-standalone-chrome/20594 |
@diemol I have the same error using the command from the docker-selenium README: sudo docker run -d --net grid -e HUB_HOST=selenium-hub -v /dev/shm:/dev/shm selenium/node-firefox:3.141.0-actinium |
This should be fixed by d54ebd7. We're preparing a new release with this fix in. |
3.141.5 has now been released, with this fix in. Share and enjoy! |
Thanks for the fix, @shs96c! Tests are running again :) |
Hi all,
After the recent update to v3.141.0 I've found that Selenium throws an exception when run on a single cpu.
During our CI process, I'm trying to run Protractor's webdriver-manager tool which depends on Selenium. To use it you typically run webdriver-manager update to get the latest drivers, e.g. Selenium, Chromedriver, etc. Then you run webdriver-manager start, which launches Selenium and Chromedriver etc.
The problem looks to happen during Jetty setup, in 'selenium/java/server/src/org/openqa/selenium/grid/server/BaseServerOptions.java' ln.61 where the max threads is set to 3 for single cpu systems
Meta -
OS: Fedora Linux
Selenium Version: 3.141.0
Browser: N/A
Browser Version: N/A
Expected Behavior -
Selenium starts normally when run on a single cpu
Actual Behavior -
Selenium throws an exception when run on a single cpu
Steps to reproduce -
Launch selenium on a system with a single cpu (we're using a vm), it should throw the following exception:
Exception in thread "main" java.lang.IllegalStateException: Insufficient configured threads: required=3 < max=3 for QueuedThreadPool[qtp707610042]@2a2d45ba{STARTED,3<=3<=3,i=3,q=0}[ReservedThreadExecutor@2f7c2f4f{s=0/1,p=0}]
The exception goes away when increasing the number of cpu's
Full output from webdriver-manager start:
The text was updated successfully, but these errors were encountered: