webdriver-update still cannot work offline, fails in case of DNS error
See original GitHub issueI saw in the changelog that “feat(start): start selenium without making web requests” #232 has been implemented, so I updated webdriver-manager to 12.0.6 in our build system.
We had some DNS problems in our network, and this has proven that unfortunately webdriver-manager still cannot work offline, even though I provide the exact versions of selenium and chrome driver (see below). These selenium and chrome driver versions have been previously installed by webdriver-manager.
webdriver-manager was started as:
webdriver-manager start --versions.standalone 3.3.1 --versions.chrome 2.29 --chrome_logs /path/to/chromedriver_7270.log --seleniumPort 7270
and now in case of a network failure I got the following error:
webdriver-manager: using global installed version 12.0.6
events.js:160
throw er; // Unhandled 'error' event
^
Error: getaddrinfo EAI_AGAIN chromedriver.storage.googleapis.com:443
at Object.exports._errnoException (util.js:1022:11)
at errnoException (dns.js:33:15)
at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:76:26)
Are you aware of this? Is webdriver-manager supposed to work fully offline with #232? It would be very nice to fix this, please, so webdriver-manager based build systems would not need to depend on Internet access. (Reproduced under Linux (Centos 7), Node.js version is 6.9.5 if that matters.)
Issue Analytics
- State:
- Created 6 years ago
- Reactions:6
- Comments:14 (2 by maintainers)
I am also facing the same issue while running Angular2 e2e tests
Error: getaddrinfo ENOTFOUND chromedriver.storage.googleapis.com chromedriver.storage.googleapis.com:443 at errnoException (dns.js:50:10) at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:92:26)
One more fail, now with api.github.com: