Skip to content
This repository was archived by the owner on Jul 29, 2024. It is now read-only.
This repository was archived by the owner on Jul 29, 2024. It is now read-only.

'directConnect: true' has issues for Chrome Driver #4887

@CassieRyu

Description

@CassieRyu

Could some please help take a look at below issue?
Here're my config files and error logs.

Config file, local.js

'use strict';

let config = require('./default').config;

config.capabilities = {
       browserName: 'chrome',
       chromeOptions: {
           'args': ['--start-maximized', 'disable-infobars', 'disable-gpu', 'incognito']
       }
     };

config.directConnect = true;

config.specs = ['../specs/*.spec.js'];

exports.config = config;

Command config

"local": "node_modules/.bin/protractor ./src/config/local.js --baseUrl=https://angularjs.org",

Command npm run local

error logs

> protractor_jasmine@1.0.0 local /Users/shanliu/Projects/protractor_jasmine
> protractor ./src/config/local.js --baseUrl=https://angularjs.org

(node:76217) [DEP0022] DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
[18:04:22] W/driverProviders - Using driver provider directConnect, but also found extra driver provider parameter(s): seleniumAddress
[18:04:22] I/launcher - Running 1 instances of WebDriver
[18:04:22] I/direct - Using ChromeDriver directly...
[18:04:22] E/direct - Error code: 135
[18:04:22] E/direct - Error message: Could not find update-config.json. Run 'webdriver-manager update' to download binaries.
[18:04:22] E/direct - Error: Could not find update-config.json. Run 'webdriver-manager update' to download binaries.
    at Direct.getNewDriver (/Users/shanliu/Projects/protractor_jasmine/node_modules/protractor/built/driverProviders/direct.js:63:31)
    at Runner.createBrowser (/Users/shanliu/Projects/protractor_jasmine/node_modules/protractor/built/runner.js:195:43)
    at q.then.then (/Users/shanliu/Projects/protractor_jasmine/node_modules/protractor/built/runner.js:339:29)
    at _fulfilled (/Users/shanliu/Projects/protractor_jasmine/node_modules/q/q.js:834:54)
    at /Users/shanliu/Projects/protractor_jasmine/node_modules/q/q.js:863:30
    at Promise.promise.promiseDispatch (/Users/shanliu/Projects/protractor_jasmine/node_modules/q/q.js:796:13)
    at /Users/shanliu/Projects/protractor_jasmine/node_modules/q/q.js:556:49
    at runSingle (/Users/shanliu/Projects/protractor_jasmine/node_modules/q/q.js:137:13)
    at flush (/Users/shanliu/Projects/protractor_jasmine/node_modules/q/q.js:125:13)
    at process._tickCallback (internal/process/next_tick.js:61:11)
[18:04:22] E/launcher - Process exited with error code 135
npm ERR! code ELIFECYCLE
npm ERR! errno 135
npm ERR! protractor_jasmine@1.0.0 local: `protractor ./src/config/local.js --baseUrl=https://angularjs.org`
npm ERR! Exit status 135
npm ERR! 
npm ERR! Failed at the protractor_jasmine@1.0.0 local script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/shanliu/.npm/_logs/2018-07-18T10_04_22_458Z-debug.log
------------------------------------------------------------

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions