SeleniumHQ / SeleniumHQ/docker-selenium
[🐛 Bug]: Firefox driver fails when used in Selenium Grid
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 8.7k
- Forks
- 2.5k
- Avg merge
- 10h 16m
- Merged PRs (30d)
- 20
Description
What happened?
When I run a very simple test locally against Chrome, Edge and Firefox, the test passes without any issue. However, if I run the same test against a Selenium Docker grid, the Firefox test seems to fail.
I created a sample project here: https://github.com/ablok/selenium-firefox-issue
Command used to start Selenium Grid with Docker (or Kubernetes)
See sample project: https://github.com/ablok/selenium-firefox-issue
Relevant log output
This is the stacktrace I see:
WebDriverError: Failed to decode response from marionette
at Object.throwDecodedError (node_modules/selenium-webdriver/lib/error.js:521:15)
at parseHttpResponse (node_modules/selenium-webdriver/lib/http.js:514:13)
at Executor.execute (node_modules/selenium-webdriver/lib/http.js:446:28)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Driver.execute (node_modules/selenium-webdriver/lib/webdriver.js:740:17)
at async Object.thenFinally [as finally] (node_modules/selenium-webdriver/lib/promise.js:100:5)
at async Context.<anonymous> (test.js:26:13)
Operating System
Mac M3
Docker Selenium version (image tag)
4.20.0-20240425
Selenium Grid chart version (chart version)
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the sample project at https://github.com/ablok/selenium-firefox-issue and reproduce the Firefox failure against the Docker Selenium image tagged 4.20.0-20240425. Inspect the failing call at test.js:26:13 and the reported “Failed to decode response from marionette” stack trace. Done means identifying and documenting a reproducible cause or correction for Firefox in the grid.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, javascript
- Domain
- devops, distributed-systems, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100