ramgiteng
commented
2 years ago Note: Please refer to the below logs from the Docker container
2022-03-29 18:05:00,708 INFO Included extra file "/etc/supervisor/conf.d/selenium.conf" during parsing
2022-03-29 18:05:00,710 INFO supervisord started with pid 8
2022-03-29 18:05:01,713 INFO spawned: 'xvfb' with pid 10
2022-03-29 18:05:01,715 INFO spawned: 'vnc' with pid 11
2022-03-29 18:05:01,716 INFO spawned: 'novnc' with pid 12
2022-03-29 18:05:01,718 INFO spawned: 'selenium-standalone' with pid 13
2022-03-29 18:05:01,722 INFO success: xvfb entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2022-03-29 18:05:01,722 INFO success: vnc entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2022-03-29 18:05:01,722 INFO success: novnc entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2022-03-29 18:05:01,722 INFO success: selenium-standalone entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2022-03-29 18:05:01,722 INFO exited: xvfb (exit status 0; expected)
2022-03-29 18:05:01,722 INFO exited: vnc (exit status 0; expected)
2022-03-29 18:05:01,724 INFO exited: novnc (exit status 0; expected)
Setting up SE_NODE_GRID_URL...
Selenium Grid Standalone configuration:
[network]
relax-checks = true
[node]
session-timeout = "300"
override-max-sessions = true
detect-drivers = false
max-sessions = 3
[[node.driver-configuration]]
display-name = "chrome"
stereotype = '{"browserName": "chrome", "browserVersion": "99.0", "platformName": "Linux"}'
max-sessions = 3
Starting Selenium Grid Standalone...
18:05:02.076 INFO [LoggingOptions.configureLogEncoding] - Using the system default encoding
18:05:02.079 INFO [OpenTelemetryTracer.createTracer] - Using OpenTelemetry for tracing
18:05:02.584 INFO [NodeOptions.getSessionFactories] - Detected 4 available processors
18:05:02.585 WARN [NodeOptions.getSessionFactories] - Overriding max recommended number of 4 concurrent sessions. Session stability and reliability might suffer!
18:05:02.585 WARN [NodeOptions.getSessionFactories] - One browser session is recommended per available processor. Safari is always limited to 1 session per host.
18:05:02.585 WARN [NodeOptions.getSessionFactories] - Overriding this value for Internet Explorer is not recommended. Issues related to parallel testing with Internet Explored won't be accepted.
18:05:02.585 WARN [NodeOptions.getSessionFactories] - Double check if enabling 'override-max-sessions' is really needed
18:05:02.631 INFO [NodeOptions.report] - Adding chrome for {"browserName": "chrome","browserVersion": "99.0","platformName": "Linux"} 3 times
18:05:02.644 INFO [Node.<init>] - Binding additional locator mechanisms: id, name, relative
18:05:02.660 INFO [GridModel.setAvailability] - Switching node 803fa2e0-6e82-4105-801d-1b175ea3f7cd (uri: http://"IPaddr":4444) from DOWN to UP
18:05:02.661 INFO [LocalDistributor.add] - Added node 803fa2e0-6e82-4105-801d-1b175ea3f7cd at http://"IPaddr":4444. Health check every 120s
18:05:02.778 INFO [Standalone.execute] - Started Selenium Standalone 4.1.3 (revision 7b1ebf28ef): http://"IPaddr":4444
unickq
diemol
nakodavati
github-actions[bot]
What happened?
Objective:
To execute Selenium tests across a number of chrome browsers in parallel within a Docker container consisting of chrome, chromedriver, and the Selenium server
The selenium script navigates to a page, gets the text of an element, and writes the text to console.
Expected Output:
For 3 iterations/sessions, the following is the expected output. Text is a placeholder for the actual text in element. Text Text Text
Actual Output:
Text
Explanation:
As shown above, I was able to only run one browser session within the container despite setting SE_NODE_MAX_SESSIONS=3 and SE_NODE_OVERRIDE_MAX_SESSIONS=true. I would like to run across 3 browsers.
We are able to successfully execute for one iteration.
Details:
OS Version: CentOS 7.5 No. of Cores: 4 Memory: 16 GB Storage: 120 GB Docker version: 1.13.1 Docker-Selenium image tag/version: 4.1.3-20220327
But, how can we run a Selenium test across a number of parallel browsers concurrently within the docker container? Please let me know if you need further details. Thanks for the support!
Command used to start Selenium Grid with Docker
Relevant log output
Operating System
CentOS 7.5
Docker Selenium version (tag)
4.1.3-20220327