We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I am on version 2.0.1 and after the tests run I get this error:
I cannot find any leads so that is why I am reaching out here. One of my co-workers gets the same error.
It's failing to run this command (same as what initiates the first run). Of course when I run npm run e2e in the terminal it works.
The terminal process "C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -Command npm run e2e" terminated with exit code: 1.
Here's some logging info:
20 verbose cwd C:\Users\Scott Floyd\projects\site2\st-site 21 verbose Windows_NT 10.0.19041 22 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "e2e" 23 verbose node v14.16.1 24 verbose npm v6.14.12 25 error code ELIFECYCLE 26 error errno 1 27 error st-site@0.0.0 e2e: `ng e2e iccmNA-e2e` 27 error Exit status 1
Any tips would be helpful, my google searches are coming up with posts circa 2011.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I am on version 2.0.1 and after the tests run I get this error:
I cannot find any leads so that is why I am reaching out here. One of my co-workers gets the same error.
It's failing to run this command (same as what initiates the first run). Of course when I run npm run e2e in the terminal it works.
The terminal process "C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -Command npm run e2e" terminated with exit code: 1.
Here's some logging info:
Any tips would be helpful, my google searches are coming up with posts circa 2011.
The text was updated successfully, but these errors were encountered: