-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue while running code in parallel configuration #21
Comments
Hey @rahulsingh3005 have you added your Browserstack username and access key in your environment variables or declared the same in your config file? If not, you can either:
OR
The error seems to be related to your environment config. Can you share more details regarding the same? |
Hi @shawnlobo96 thanks for responding. |
Hi @shawnlobo96 do we have any update? |
@rahulsingh3005 I couldn't replicate this error on a windows machine using the config shared, can you share any additional changes made to the repo aside form the credentials |
Hi @RohanImmanuel I have not made any change apart from the credentials. |
@rahulsingh3005 a screen share session can help us debug this better |
@rahulsingh3005 could check if the linked fork resolves your issue PR: #22 |
Hi Team,
Tried running code for parallel config. Below is the error stack I am getting on console. Need help. Am I missing out some configuration?
c:\Users\rsingh\cucumber-js-browserstack-master>npm run parallel
events.js:298
throw er; // Unhandled 'error' event
^
Error: spawn /usr/bin/env ENOENT
←[90m at Process.ChildProcess._handle.onexit (internal/child_process.js:267:19)←[39m
←[90m at onErrorNT (internal/child_process.js:467:16)←[39m
←[90m at processTicksAndRejections (internal/process/task_queues.js:84:21)←[39m
Emitted 'error' event on ChildProcess instance at:
←[90m at Process.ChildProcess._handle.onexit (internal/child_process.js:273:12)←[39m
←[90m at onErrorNT (internal/child_process.js:467:16)←[39m
←[90m at processTicksAndRejections (internal/process/task_queues.js:84:21)←[39m {
errno: ←[33m-4058←[39m,
code: ←[32m'ENOENT'←[39m,
syscall: ←[32m'spawn /usr/bin/env'←[39m,
path: ←[32m'/usr/bin/env'←[39m,
spawnargs: [
←[32m'node'←[39m,
←[32m'./node_modules/.bin/cucumber-js'←[39m,
←[32m'features/single.feature'←[39m
]
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] parallel:
cross-env CONFIG_FILE=parallel ./scripts/cucumber-runner.js features/single.feature
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] parallel 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! \servfs\RDSFolderRedirection$\rsingh\Application Data\npm-cache_logs\2020-03-12T09_52_33_612Z-debug.log
The text was updated successfully, but these errors were encountered: