You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[email protected] local D:\repos\github\nightwatch-browserstack
node scripts/local.runner.js -c conf/local.conf.js
Connecting local
D:\repos\github\nightwatch-browserstack\scripts\local.runner.js:14
if (error) throw error;
^
LocalError
at D:\repos\github\nightwatch-browserstack\node_modules\browserstack-local\lib\Local.js:58:20
at ChildProcess.exithandler (child_process.js:285:7)
at ChildProcess.emit (events.js:198:13)
at maybeClose (internal/child_process.js:982:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] local: node scripts/local.runner.js -c conf/local.conf.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] local script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
D:\repos\github\nightwatch-browserstack\scripts\local.runner.js:14
if (error) throw error;
^
LocalError
at D:\repos\github\nightwatch-browserstack\node_modules\browserstack-local\lib\Local.js:58:20
at ChildProcess.exithandler (child_process.js:285:7)
at ChildProcess.emit (events.js:198:13)
at maybeClose (internal/child_process.js:982:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] parallel_local: node scripts/local.runner.js -c conf/parallel_local.conf.js -e chrome,firefox,safari
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] parallel_local script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
The text was updated successfully, but these errors were encountered:
The error you received was since the local testing binary did not start. This could happen if you are behind a proxy and the local testing binary was unable to connect to Browserstack's infrastructure.
Check with your network team if traffic to *.browserstack.com is whitelisted on ports 80 and 443 and WebSocket traffic is allowed to pass through?
Can you also manually run the binary on your machine and share the console output?
Run it in the terminal/cmd prompt
Mac OS/ Linux: ./BrowserStackLocal --key <BROWSERSTACK_ACCESS_KEY>
Windows: BrowserStackLocal.exe --key <BROWSERSTACK_ACCESS_KEY>
nightwatch-browserstack>npm run local
Connecting local
D:\repos\github\nightwatch-browserstack\scripts\local.runner.js:14
if (error) throw error;
^
LocalError
at D:\repos\github\nightwatch-browserstack\node_modules\browserstack-local\lib\Local.js:58:20
at ChildProcess.exithandler (child_process.js:285:7)
at ChildProcess.emit (events.js:198:13)
at maybeClose (internal/child_process.js:982:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] local:
node scripts/local.runner.js -c conf/local.conf.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] local script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
nightwatch-browserstack>npm run parallel_local
Connecting local
D:\repos\github\nightwatch-browserstack\scripts\local.runner.js:14
if (error) throw error;
^
LocalError
at D:\repos\github\nightwatch-browserstack\node_modules\browserstack-local\lib\Local.js:58:20
at ChildProcess.exithandler (child_process.js:285:7)
at ChildProcess.emit (events.js:198:13)
at maybeClose (internal/child_process.js:982:16)
at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] parallel_local:
node scripts/local.runner.js -c conf/parallel_local.conf.js -e chrome,firefox,safari
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] parallel_local script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
The text was updated successfully, but these errors were encountered: