Travis builds failing on some Selenium error
- Dominant language
- JavaScript
- Stars
- 5.8k
- Forks
- 585
- PR merge metrics
- No merged PRs in 30d
Description
``````
> node test/index
/home/travis/build/imsky/holder/node_modules/webdriverio/lib/utils/PromiseHandler.js:154
throw error;
^
RuntimeError: RuntimeError
(ECONNREFUSED:-1) Couldn't connect to selenium server
Problem: Couldn't connect to selenium server
Callstack:
-> init()
npm ERR! Test failed. See above for more details.
The command "npm test" exited with 1.
Done. Your build exited with 1.```
``````
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by running `node test/index` and reviewing the Travis `npm test` output, especially the webdriverio PromiseHandler.js failure. Identify why the Selenium server connection is refused in Travis and verify that the affected build completes successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- ci-cd, testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100