wdio-devtools-debug-log

Sending build context to Docker daemon  752.1kB
Step 1/12 : FROM node:12
 ---> da572e0d48fc
Step 2/12 : RUN mkdir -p /home/node/app/node_modules && chown -R node:node /home/node/app
 ---> Using cache
 ---> bc35d1ec1d7c
Step 3/12 : WORKDIR /home/node/app
 ---> Using cache
 ---> 7ad6028cb53b
Step 4/12 : RUN apt-get update &&  apt-get install -y git-all gconf-service libasound2 libatk1.0-0 libc6 libcairo2 libcups2 libdbus-1-3     libexpat1 libfontconfig1 libgcc1 libgconf-2-4 libgdk-pixbuf2.0-0 libglib2.0-0 libgtk-3-0     libnspr4 libpango-1.0-0 libpangocairo-1.0-0 libstdc++6 libx11-6 libx11-xcb1 libxcb1 libxcomposite1     libxcursor1 libxdamage1 libxext6 libxfixes3 libxi6 libxrandr2 libxrender1 libxss1 libxtst6 ca-certificates     fonts-liberation libappindicator1 libappindicator3-1 libnss3 lsb-release xdg-utils apt-utils xvfb
 ---> Using cache
 ---> 4f53cab08052
Step 5/12 : RUN wget https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb
 ---> Using cache
 ---> 2ebd42c4c57b
Step 6/12 : RUN dpkg -i google-chrome-stable_current_amd64.deb; apt-get -fy install
 ---> Using cache
 ---> 682cec809738
Step 7/12 : RUN whereis google-chrome
 ---> Using cache
 ---> f2717130ab20
Step 8/12 : COPY package*.json ./
 ---> Using cache
 ---> f8f6fedab589
Step 9/12 : USER node
 ---> Using cache
 ---> f0331f8545c0
Step 10/12 : RUN npm install
 ---> Using cache
 ---> e4d128628c78
Step 11/12 : COPY --chown=node:node . .
 ---> 6f53189457ac
Step 12/12 : RUN npm test
 ---> Running in 6918925c62c7

> wdio-chromeDevTools@1.0.0 test /home/node/app
> npm run wdio -- ./wdio.conf.js


> wdio-chromeDevTools@1.0.0 wdio /home/node/app
> node -r @babel/register ./node_modules/.bin/wdio "./wdio.conf.js"


Execution of 1 spec files started at 2019-09-11T12:08:24.619Z

2019-09-11T12:08:24.623Z DEBUG @wdio/utils:initialiseServices: initialise wdio service "chromedriver"
2019-09-11T12:08:24.651Z DEBUG @wdio/utils:initialiseServices: initialise wdio service "devtools"
2019-09-11T12:08:24.840Z INFO @wdio/cli:Launcher: Run onPrepare hook
Starting ChromeDriver 76.0.3809.126 (d80a294506b4c9d18015e755cee48f953ddc3f2f-refs/branch-heads/3809@{#1024}) on port 4444
Only local connections are allowed.
Please protect ports used by ChromeDriver and related test frameworks to prevent access by malicious code.
[1568203704.851][SEVERE]: bind() failed: Cannot assign requested address (99)
2019-09-11T12:08:24.861Z INFO @wdio/local-runner: Start worker 0-0 with arg: ./wdio.conf.js
[0-0] RUNNING in chrome - /test/specs/devtools.spec.js
[0-0] 2019-09-11T12:08:25.172Z INFO @wdio/local-runner: Run worker command: run
[0-0] 2019-09-11T12:08:25.180Z DEBUG @wdio/utils:initialiseServices: initialise wdio service "chromedriver"
[0-0] 2019-09-11T12:08:25.212Z DEBUG @wdio/utils:initialiseServices: initialise wdio service "devtools"
[0-0] 2019-09-11T12:08:25.369Z DEBUG @wdio/local-runner:utils: init remote session
[0-0] 2019-09-11T12:08:25.406Z INFO webdriver: [POST] http://127.0.0.1:4444/session
[0-0] 2019-09-11T12:08:25.406Z INFO webdriver: DATA {
  capabilities: {
    alwaysMatch: { browserName: 'chrome', 'goog:chromeOptions': [Object] },
    firstMatch: [ {} ]
  },
  desiredCapabilities: { browserName: 'chrome', 'goog:chromeOptions': { args: [Array] } }
}
[0-0] 2019-09-11T12:08:25.595Z DEBUG webdriver: request failed due to response error: unknown error
[0-0] 2019-09-11T12:08:25.595Z WARN webdriver: Request failed due to unknown error: Chrome failed to start: exited abnormally
  (unknown error: DevToolsActivePort file doesn't exist)
  (The process started from chrome location /usr/bin/google-chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
[0-0] 2019-09-11T12:08:25.596Z INFO webdriver: Retrying 1/3
2019-09-11T12:08:25.596Z INFO webdriver: [POST] http://127.0.0.1:4444/session
[0-0] 2019-09-11T12:08:25.596Z INFO webdriver: DATA {
  capabilities: {
    alwaysMatch: { browserName: 'chrome', 'goog:chromeOptions': [Object] },
    firstMatch: [ {} ]
  },
  desiredCapabilities: { browserName: 'chrome', 'goog:chromeOptions': { args: [Array] } }
}
[0-0] 2019-09-11T12:08:25.759Z DEBUG webdriver: request failed due to response error: unknown error
[0-0] 2019-09-11T12:08:25.760Z INFO webdriver: Retrying 2/3
2019-09-11T12:08:25.760Z INFO webdriver: [POST] http://127.0.0.1:4444/session
[0-0] 2019-09-11T12:08:25.760Z WARN webdriver: Request failed due to unknown error: Chrome failed to start: exited abnormally
  (unknown error: DevToolsActivePort file doesn't exist)
  (The process started from chrome location /usr/bin/google-chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
[0-0] 2019-09-11T12:08:25.760Z INFO webdriver: DATA {
  capabilities: {
    alwaysMatch: { browserName: 'chrome', 'goog:chromeOptions': [Object] },
    firstMatch: [ {} ]
  },
  desiredCapabilities: { browserName: 'chrome', 'goog:chromeOptions': { args: [Array] } }
}
[0-0] 2019-09-11T12:08:25.918Z DEBUG webdriver: request failed due to response error: unknown error
[0-0] 2019-09-11T12:08:25.918Z INFO webdriver: Retrying 3/3
2019-09-11T12:08:25.918Z INFO webdriver: [POST] http://127.0.0.1:4444/session
[0-0] 2019-09-11T12:08:25.918Z WARN webdriver: Request failed due to unknown error: Chrome failed to start: exited abnormally
  (unknown error: DevToolsActivePort file doesn't exist)
  (The process started from chrome location /usr/bin/google-chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
[0-0] 2019-09-11T12:08:25.918Z INFO webdriver: DATA {
  capabilities: {
    alwaysMatch: { browserName: 'chrome', 'goog:chromeOptions': [Object] },
    firstMatch: [ {} ]
  },
  desiredCapabilities: { browserName: 'chrome', 'goog:chromeOptions': { args: [Array] } }
}
[0-0] 2019-09-11T12:08:26.076Z DEBUG webdriver: request failed due to response error: unknown error
[0-0] 2019-09-11T12:08:26.076Z ERROR webdriver: Request failed due to unknown error: unknown error: Chrome failed to start: exited abnormally
  (unknown error: DevToolsActivePort file doesn't exist)
  (The process started from chrome location /usr/bin/google-chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
    at getErrorFromResponseBody (/home/node/app/node_modules/webdriver/build/utils.js:351:10)
    at Request._callback (/home/node/app/node_modules/webdriver/build/request.js:121:64)
    at Request.self.callback (/home/node/app/node_modules/request/request.js:185:22)
    at Request.emit (events.js:209:13)
    at Request.EventEmitter.emit (domain.js:476:20)
    at Request.<anonymous> (/home/node/app/node_modules/request/request.js:1161:10)
    at Request.emit (events.js:209:13)
    at Request.EventEmitter.emit (domain.js:476:20)
    at IncomingMessage.<anonymous> (/home/node/app/node_modules/request/request.js:1083:12)
    at Object.onceWrapper (events.js:298:28)
[0-0] 2019-09-11T12:08:26.077Z ERROR @wdio/runner: unknown error: unknown error: Chrome failed to start: exited abnormally
  (unknown error: DevToolsActivePort file doesn't exist)
  (The process started from chrome location /usr/bin/google-chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
    at getErrorFromResponseBody (/home/node/app/node_modules/webdriver/build/utils.js:351:10)
    at Request._callback (/home/node/app/node_modules/webdriver/build/request.js:121:64)
    at Request.self.callback (/home/node/app/node_modules/request/request.js:185:22)
    at Request.emit (events.js:209:13)
    at Request.EventEmitter.emit (domain.js:476:20)
    at Request.<anonymous> (/home/node/app/node_modules/request/request.js:1161:10)
    at Request.emit (events.js:209:13)
    at Request.EventEmitter.emit (domain.js:476:20)
    at IncomingMessage.<anonymous> (/home/node/app/node_modules/request/request.js:1083:12)
    at Object.onceWrapper (events.js:298:28)
0-0 worker error {
  name: 'unknown error',
  message: 'unknown error: Chrome failed to start: exited abnormally\n' +
    "  (unknown error: DevToolsActivePort file doesn't exist)\n" +
    '  (The process started from chrome location /usr/bin/google-chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)',
  stack: 'unknown error: unknown error: Chrome failed to start: exited abnormally\n' +
    "  (unknown error: DevToolsActivePort file doesn't exist)\n" +
    '  (The process started from chrome location /usr/bin/google-chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)\n' +
    '    at getErrorFromResponseBody (/home/node/app/node_modules/webdriver/build/utils.js:351:10)\n' +
    '    at Request._callback (/home/node/app/node_modules/webdriver/build/request.js:121:64)\n' +
    '    at Request.self.callback (/home/node/app/node_modules/request/request.js:185:22)\n' +
    '    at Request.emit (events.js:209:13)\n' +
    '    at Request.EventEmitter.emit (domain.js:476:20)\n' +
    '    at Request.<anonymous> (/home/node/app/node_modules/request/request.js:1161:10)\n' +
    '    at Request.emit (events.js:209:13)\n' +
    '    at Request.EventEmitter.emit (domain.js:476:20)\n' +
    '    at IncomingMessage.<anonymous> (/home/node/app/node_modules/request/request.js:1083:12)\n' +
    '    at Object.onceWrapper (events.js:298:28)'
}
[0-0] 2019-09-11T12:08:26.078Z ERROR @wdio/local-runner: Failed launching test session: TypeError: Cannot read property 'capabilities' of null
    at Runner.run (/home/node/app/node_modules/@wdio/runner/build/index.js:91:74)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
2019-09-11T12:08:26.091Z DEBUG @wdio/local-runner: Runner 0-0 finished with exit code 1
[0-0] FAILED in chrome - /test/specs/devtools.spec.js
2019-09-11T12:08:26.093Z INFO @wdio/cli:Launcher: Run onComplete hook

Spec Files:      0 passed, 1 failed, 1 total (100% completed) in 00:00:01 

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! wdio-chromeDevTools@1.0.0 wdio: `node -r @babel/register ./node_modules/.bin/wdio "./wdio.conf.js"`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the wdio-chromeDevTools@1.0.0 wdio 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!     /home/node/.npm/_logs/2019-09-11T12_08_26_128Z-debug.log
npm ERR! Test failed.  See above for more details.
The command '/bin/sh -c npm test' returned a non-zero code: 1