angular / protractor

E2E test framework for Angular apps
http://www.protractortest.org
MIT License
8.75k stars 2.31k forks source link

Unable to run test on chrome 80+. E/launcher - connect ECONNREFUSED 127.0.0.1:443 #5527

Closed ashinzekene closed 3 years ago

ashinzekene commented 3 years ago

Bug report

exports.config = config;

- A relevant example test
Running

webdriver-manager update webdriver-manager start protactor conf.js


Output
webdriver-manager update

I/file_manager - creating folder C:\npm\prefix\node_modules\protractor\node_modules\webdriver-manager\selenium I/config_source - curl -oC:\npm\prefix\node_modules\protractor\node_modules\webdriver-manager\selenium\standalone-response.xml https://selenium-release.storage.googleapis.com/ I/config_source - curl -oC:\npm\prefix\node_modules\protractor\node_modules\webdriver-manager\selenium\chrome-response.xml https://chromedriver.storage.googleapis.com/ I/config_source - curl -oC:\npm\prefix\node_modules\protractor\node_modules\webdriver-manager\selenium\gecko-response.json https://api.github.com/repos/mozilla/geckodriver/releases I/downloader - curl -oC:\npm\prefix\node_modules\protractor\node_modules\webdriver-manager\selenium/selenium-server-standalone-3.141.59.jar https://selenium-release.storage.googleapis.com/3.141/selenium-server-standalone-3.141.59.jar I/downloader - curl -oC:\npm\prefix\node_modules\protractor\node_modules\webdriver-manager\selenium/chromedriver_92.0.4515.107.zip https://chromedriver.storage.googleapis.com/92.0.4515.43/chromedriver_win32.zip I/downloader - curl -oC:\npm\prefix\node_modules\protractor\node_modules\webdriver-manager\selenium/geckodriver-v0.29.1.zip https://github.com/mozilla/geckodriver/releases/download/v0.29.1/geckodriver-v0.29.1-win64.zip I/update - geckodriver: unzipping geckodriver-v0.29.1.zip I/update - chromedriver: unzipping chromedriver_92.0.4515.107.zip


webdriver-manager start

[15:54:09] I/start - java -Dwebdriver.gecko.driver=C:\npm\prefix\node_modules\protractor\node_modules\webdriver-manager\selenium\geckodriver-v0.29.1.exe -Dwebdriver.chrome.driver=C:\npm\prefix\node_modules\protractor\node_modules\webdriver-manager\selenium\chromedriver_92.0.4515.107.exe -jar C:\npm\prefix\node_modules\protractor\node_modules\webdriver-manager\selenium\selenium-server-standalone-3.141.59.jar -port 4444 [15:54:09] I/start - seleniumProcess.pid: 1772 15:54:10.526 INFO [GridLauncherV3.parse] - Selenium server version: 3.141.59, revision: e82be7d358 15:54:10.703 INFO [GridLauncherV3.lambda$buildLaunchers$3] - Launching a standalone Selenium Server on port 4444 2021-08-09 15:54:10.854:INFO::main: Logging initialized @1135ms to org.seleniumhq.jetty9.util.log.StdErrLog 15:54:11.321 INFO [WebDriverServlet.] - Initialising WebDriverServlet 15:54:11.657 INFO [SeleniumServer.boot] - Selenium Server is up and running on port 4444 [15:54:11] I/start - Everything started [15:54:11] I/start - Detached pid: 6424

protactor conf.js

pistore-integration-test@1.0.0 protractor D:\a\r1\a\drop\Deployment\Test\Protractor protractor "conf.js" "--params.login.adminUserName=***"

[15:54:19] W/launcher - You have specified both capabilities and multiCapabilities. This will result in capabilities being ignored [15:54:19] I/launcher - Running 1 instances of WebDriver [15:54:19] I/hosted - Using the selenium server at http://localhost:4444/wd/hub [15:54:22] W/runner - Ignoring unknown extra flags: base-url. This will be an error in future versions, please use --disableChecks flag to disable the Protractor CLI flag checks. pretest.run [15:54:23] E/launcher - connect ECONNREFUSED 127.0.0.1:443 [15:54:23] E/launcher - Error: connect ECONNREFUSED 127.0.0.1:443 at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1148:16) [15:54:23] E/launcher - Process exited with error code 199


Specifying a version higher than chrome 79 gives the same error, on 79 or lower error is

pistore-integration-test@1.0.0 protractor D:\a\r1\a\drop\Deployment\Test\Protractor protractor "conf.js" "--params.login.adminUserName=***"

[15:39:30] W/launcher - You have specified both capabilities and multiCapabilities. This will result in capabilities being ignored [15:39:30] I/launcher - Running 1 instances of WebDriver [15:39:30] I/hosted - Using the selenium server at http://localhost:4444/wd/hub [15:39:34] E/launcher - unknown error: cannot find Chrome binary Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:25:53' System info: host: 'fv-az26-910', ip: '10.1.0.17', os.name: 'Windows Server 2019', os.arch: 'amd64', os.version: '10.0', java.version: '1.8.0_292' Driver info: driver.version: unknown remote stacktrace: Backtrace: Ordinal0 [0x0110A113+1548563] Ordinal0 [0x0108DDA1+1039777] Ordinal0 [0x0100E485+517253] Ordinal0 [0x00F9C0F1+49393] Ordinal0 [0x00FBB797+178071] Ordinal0 [0x00FBB59D+177565] Ordinal0 [0x00FB95FB+169467] Ordinal0 [0x00FA160A+71178] Ordinal0 [0x00FA2690+75408] Ordinal0 [0x00FA2629+75305] Ordinal0 [0x010A71B7+1143223] GetHandleVerifier [0x011A2B46+507814] GetHandleVerifier [0x011A2864+507076] GetHandleVerifier [0x011A9F47+537511] GetHandleVerifier [0x011A3402+510050] Ordinal0 [0x0109F29C+1110684] Ordinal0 [0x010A938B+1151883] Ordinal0 [0x010A94F3+1152243] Ordinal0 [0x010A83F5+1147893] BaseThreadInitThunk [0x77910419+25] RtlGetAppContainerNamedObjectPath [0x77EA72FD+237] RtlGetAppContainerNamedObjectPath [0x77EA72CD+189]

[15:39:34] E/launcher - WebDriverError: unknown error: cannot find Chrome binary Build info: version: '3.141.59', revision: 'e82be7d358', time: '2018-11-14T08:25:53' System info: host: 'fv-az26-910', ip: '10.1.0.17', os.name: 'Windows Server 2019', os.arch: 'amd64', os.version: '10.0', java.version: '1.8.0_292' Driver info: driver.version: unknown remote stacktrace: Backtrace: Ordinal0 [0x0110A113+1548563] Ordinal0 [0x0108DDA1+1039777] Ordinal0 [0x0100E485+517253] Ordinal0 [0x00F9C0F1+49393] Ordinal0 [0x00FBB797+178071] Ordinal0 [0x00FBB59D+177565] Ordinal0 [0x00FB95FB+169467] Ordinal0 [0x00FA160A+71178] Ordinal0 [0x00FA2690+75408] Ordinal0 [0x00FA2629+75305] Ordinal0 [0x010A71B7+1143223] GetHandleVerifier [0x011A2B46+507814] GetHandleVerifier [0x011A2864+507076] GetHandleVerifier [0x011A9F47+537511] GetHandleVerifier [0x011A3402+510050] Ordinal0 [0x0109F29C+1110684] Ordinal0 [0x010A938B+1151883] Ordinal0 [0x010A94F3+1152243] Ordinal0 [0x010A83F5+1147893] BaseThreadInitThunk [0x77910419+25] RtlGetAppContainerNamedObjectPath [0x77EA72FD+237] RtlGetAppContainerNamedObjectPath [0x77EA72CD+189]

 at Object.checkLegacyResponse (D:\a\r1\a\drop\Deployment\Test\Protractor\node_modules\selenium-webdriver\lib\error.js:546:15)
 at parseHttpResponse (D:\a\r1\a\drop\Deployment\Test\Protractor\node_modules\selenium-webdriver\lib\http.js:509:13)
 at D:\a\r1\a\drop\Deployment\Test\Protractor\node_modules\selenium-webdriver\lib\http.js:441:30
 at processTicksAndRejections (internal/process/task_queues.js:95:5)

From: Task: WebDriver.createSession() at Function.createSession (D:\a\r1\a\drop\Deployment\Test\Protractor\node_modules\selenium-webdriver\lib\webdriver.js:769:24) at Function.createSession (D:\a\r1\a\drop\Deployment\Test\Protractor\node_modules\selenium-webdriver\chrome.js:761:15) at createDriver (D:\a\r1\a\drop\Deployment\Test\Protractor\node_modules\selenium-webdriver\index.js:170:33) at Builder.build (D:\a\r1\a\drop\Deployment\Test\Protractor\node_modules\selenium-webdriver\index.js:626:16) at Hosted.getNewDriver (D:\a\r1\a\drop\Deployment\Test\Protractor\node_modules\protractor\built\driverProviders\driverProvider.js:53:33) at Runner.createBrowser (D:\a\r1\a\drop\Deployment\Test\Protractor\node_modules\protractor\built\runner.js:195:43) at D:\a\r1\a\drop\Deployment\Test\Protractor\node_modules\protractor\built\runner.js:339:29 at _fulfilled (D:\a\r1\a\drop\Deployment\Test\Protractor\node_modules\q\q.js:834:54) at D:\a\r1\a\drop\Deployment\Test\Protractor\node_modules\q\q.js:863:30 at Promise.promise.promiseDispatch (D:\a\r1\a\drop\Deployment\Test\Protractor\node_modules\q\q.js:796:13) [15:39:34] E/launcher - Process exited with error code 199



Feature Request
---

- Reasons for adopting new feature
- Is this a breaking change? (How will this affect existing functionality)
StanislavKharchenko commented 3 years ago

How you open testing application? Is it available by host 127.0.0.1:443 ?

ashinzekene commented 3 years ago

My bad, I specified the wrong url