What happened?
This is more a question than a issue. I see that images with chrome 95 are only being published with selenium 4.0.
I've migrated to selenium 4.0 in the client, however, we are still using selenium grid 3.0 in our selenium server. We run 80+ headless tests in parallel with chrome, it works with selenium grid 3 but it doesn't with 4.0, it's just too slow for some reason.
I would like to report on that issue, but I don't feel I can provide a lot of details, so I will stick to 3.0 until I see this issue fixed.
My question is if you will still provide selenium 3.0 images with new browsers, just to see what we can do.
Thanks.
Command used to start Selenium Grid with Docker
This is the docker compose file used for 4.0, but it's not relevant for the issue
version: "3"
services:
selenium-hub4:
image: selenium/hub:4.0.0-20211013
container_name: selenium-hub4
restart: unless-stopped
ports:
- "4442:4442"
- "4443:4443"
- "4444:4444"
environment:
- JAVA_OPTS=-Xmx10g -XX:-ClassUnloading -XX:-ClassUnloadingWithConcurrentMark -Dselenium.LOGGER.level=WARNING
- SE_NODE_SESSION_TIMEOUT=200
chrome-node4:
image: selenium/node-chrome:4.0.0-20211013
container_name: selenium-chrome-node4
restart: unless-stopped
shm_size: 16gb
depends_on:
- selenium-hub4
environment:
- SE_EVENT_BUS_HOST=selenium-hub4
- SE_EVENT_BUS_PUBLISH_PORT=4442
- SE_EVENT_BUS_SUBSCRIBE_PORT=4443
- JAVA_OPTS=-Xmx10g -XX:-ClassUnloading -XX:-ClassUnloadingWithConcurrentMark -Dselenium.LOGGER.level=WARNING
- SCREEN_WIDTH=1366
- SCREEN_HEIGHT=768
- SCREEN_DEPTH=24
- SCREEN_DPI=74
- START_XVFB=false
- SE_NODE_MAX_SESSIONS=65
- SE_NODE_OVERRIDE_MAX_SESSIONS=true
- SE_SESSION_RETRY_INTERVAL=1
- SE_NODE_SESSION_TIMEOUT=200
ports:
- "6900:5900"
logging:
options:
max-size: 50m
This is the one used for selenium 3.0:
version: "3"
services:
selenium-hub:
image: selenium/hub:3.141.59-20210929
container_name: selenium-hub
restart: unless-stopped
ports:
- "5444:4444"
privileged: true
environment:
GRID_BROWSER_TIMEOUT: 320
GRID_TIMEOUT: 320
NODE_BROWSER_TIMEOUT: 320
NODE_TIMEOUT: 320
JAVA_OPTS: -Xmx10g -XX:-ClassUnloading -XX:-ClassUnloadingWithConcurrentMark -Dselenium.LOGGER.level=WARNING
GRID_CLEAN_UP_CYCLE=60000
logging:
options:
max-size: 50m
chrome-node:
image: selenium/node-chrome:3.141.59-20210929
container_name: selenium-chrome-node
restart: unless-stopped
shm_size: 16gb
tmpfs:
- /tmp
environment:
REMOTE_HOST: http://chrome-node:5555
HUB_HOST: selenium-hub
NODE_MAX_INSTANCES: 10
NODE_MAX_SESSION: 100
GRID_BROWSER_TIMEOUT: 320
GRID_TIMEOUT: 320
NODE_BROWSER_TIMEOUT: 320
NODE_TIMEOUT: 320
START_XVFB: "false"
DBUS_SESSION_BUS_ADDRESS: "/dev/null"
JAVA_OPTS: -Xmx10g -XX:-ClassUnloading -XX:-ClassUnloadingWithConcurrentMark -Dselenium.LOGGER.level=WARNING
privileged: true
extra_hosts:
- "DEVELOPMENT:192.168.130.5"
- "PREPRODUCTION:192.168.131.5"
- "PRODUCTION:192.168.132.5"
- "JENKINS:192.168.130.4"
logging:
options:
max-size: 50mRelevant log output
Operating System
Ubuntu 20.04 LTS
Docker Selenium version (tag)
3.141.59-20210929
What happened?
This is more a question than a issue. I see that images with chrome 95 are only being published with selenium 4.0.
I've migrated to selenium 4.0 in the client, however, we are still using selenium grid 3.0 in our selenium server. We run 80+ headless tests in parallel with chrome, it works with selenium grid 3 but it doesn't with 4.0, it's just too slow for some reason.
I would like to report on that issue, but I don't feel I can provide a lot of details, so I will stick to 3.0 until I see this issue fixed.
My question is if you will still provide selenium 3.0 images with new browsers, just to see what we can do.
Thanks.
Command used to start Selenium Grid with Docker
Relevant log output
Operating System
Ubuntu 20.04 LTS
Docker Selenium version (tag)
3.141.59-20210929