Open satishautade opened 6 years ago
any updates to the topic?
hi but it's no gemini problem but chromedriver that limit your maximum connect count and reject connection
@sipayRT is there a way to limit number of simultaneous connections ?
@sipayRT The tests are being run in series, not in parallel, so we expect the available connections to be reused - perhaps it is a problem closing the connections somewhere?
you can use suitesPerSession
and sessionsPerBrowser
options to configure working with browser sessions. See docs about it - https://gemini-testing.github.io/doc/config.html
Had the same problem. Solved it by running chromedriver via process.execFile:
import chromedriver from 'chromedriver'
const args = ['--port=4444', '--url-base=wd/hub']
chromeDriverChildProcess = childProcess.execFile(chromedriver.path, args, () => {
//...
})
Stopping via chromeDriverChildProcess.kill()
I suspect if there is a maximum limit on the connections to the chromedriver somewhere. Shouldn't the same connection to chromedriver be reused for each test? Here is the test setup code Using
gemini --version
: 5.0.0-alpha.8 ....gemini.conf.js
file:gemini-runner.js
file:Test source code:
Command used to run the test:
Result: This test suite takes array of about 60 page URLs (from ctx) and captures screenshots for each page. If we just use the chromedriver then first 9 URLs are hit and tests are run for them. But anything from 10th page URL starts failing as it is unable to connect to chromedriver with following error
...
Expected behaviour: It should run through all the page URLs like it does for first 9.
...