I know this is the most common issue with Testcafe, but I previously posted questions and solutions doesn't match/work to resolve my issue. Testcafe version 1.8.4, with allure reporting. I have configured few test suites running sequential in my project but, after first suite run Testcafe terminates with the following error and aborts the test run.
npm ERR! code ELIFECYCLE
npm ERR! errno 4
npm ERR! user-journey-tests#1.0.0 test:appjourneys:azure: `TARGET_ENV=test DATA_CENTER=azwus2 testcafe 'chromium:headless:emulation' './journeys/app-journeys/*-spec.js' -r allure`
npm ERR! Exit status 4
npm ERR!
npm ERR! Failed at the user-journey-tests#1.0.0 test:appjourneys:azure 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/Venkat/.npm/_logs/2020-05-27T03_13_43_108Z-debug.log
Below is the debug log
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli '/usr/local/Cellar/node/12.10.0/bin/node',
1 verbose cli '/usr/local/bin/npm',
1 verbose cli 'run',
1 verbose cli 'test:appjourneys:azure'
1 verbose cli ]
2 info using npm#6.11.3
3 info using node#v12.10.0
4 verbose run-script [
4 verbose run-script 'pretest:appjourneys:azure',
4 verbose run-script 'test:appjourneys:azure',
4 verbose run-script 'posttest:appjourneys:azure'
4 verbose run-script ]
5 info lifecycle user-journey-tests#1.0.0~pretest:appjourneys:azure: user-journey-tests#1.0.0
6 info lifecycle user-journey-tests#1.0.0~test:appjourneys:azure: user-journey-tests#1.0.0
7 verbose lifecycle user-journey-tests#1.0.0~test:appjourneys:azure: unsafe-perm in lifecycle true
8 verbose lifecycle user-journey-tests#1.0.0~test:appjourneys:azure: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/Venkat/GAP/store-service/user-journeys-testcafe/node_modules/.bin:/usr/local/Cellar/maven/3.6.0/bin:/Library/Java/JavaVirtualMachines/jdk1.8.0_131.jdk/Contents/Home/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/Cellar/maven/3.6.0/bin:/Library/Java/JavaVirtualMachines/jdk1.8.0_131.jdk/Contents/Home/bin
9 verbose lifecycle user-journey-tests#1.0.0~test:appjourneys:azure: CWD: /Users/Venkat/GAP/store-service/user-journeys-testcafe
10 silly lifecycle user-journey-tests#1.0.0~test:appjourneys:azure: Args: [
10 silly lifecycle '-c',
10 silly lifecycle "TARGET_ENV=test DATA_CENTER=azwus2 testcafe 'chromium:headless:emulation' './journeys/app-journeys/*-spec.js' -r allure"
10 silly lifecycle ]
11 silly lifecycle user-journey-tests#1.0.0~test:appjourneys:azure: Returned: code: 4 signal: null
12 info lifecycle user-journey-tests#1.0.0~test:appjourneys:azure: Failed to exec test:appjourneys:azure script
13 verbose stack Error: user-journey-tests#1.0.0 test:appjourneys:azure: `TARGET_ENV=test DATA_CENTER=azwus2 testcafe 'chromium:headless:emulation' './journeys/app-journeys/*-spec.js' -r allure`
13 verbose stack Exit status 4
13 verbose stack at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:209:13)
13 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:209:13)
13 verbose stack at maybeClose (internal/child_process.js:1021:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
14 verbose pkgid user-journey-tests#1.0.0
15 verbose cwd /Users/Venkat/GAP/store-service/user-journeys-testcafe
16 verbose Darwin 17.7.0
17 verbose argv "/usr/local/Cellar/node/12.10.0/bin/node" "/usr/local/bin/npm" "run" "test:appjourneys:azure"
18 verbose node v12.10.0
19 verbose npm v6.11.3
20 error code ELIFECYCLE
21 error errno 4
22 error user-journey-tests#1.0.0 test:appjourneys:azure: `TARGET_ENV=test DATA_CENTER=azwus2 testcafe 'chromium:headless:emulation' './journeys/app-journeys/*-spec.js' -r allure`
22 error Exit status 4
23 error Failed at the user-journey-tests#1.0.0 test:appjourneys:azure script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 4, true ]
I tried the following:
npm -clean install
update testcafe to latest version 1.8.4 3.
I merged my suite in to one single npm run <cmd> - This helps to run the tests but still the error continues to show up at the end and build status is unstable. Any thoughts how to over come this?
I see the following error in the NPM log:
Error: user-journey-tests#1.0.0 test:appjourneys:azure: \\`TARGET_ENV=test DATA_CENTER=azwus2 testcafe 'chromium:headless:emulation' './journeys/app-journeys/*-spec.js' -r allure\\`
Exit status 4
at EventEmitter.<anonymous>
It means that TestCafe finished tests with exit code 4.
TestCafe finishes with a non-zero exit code when some tests fail during your test session. In this particular case, 4 tests failed.
If you want to disable test failure indication via exit codes, you can append || exit 0 to the TestCafe command.
Related
I'm a graphic student trying to learn something further than classic HTML/CSS.
I want to build the default Next.js app, which you can get by npm create-next-app filename.
It certainly works when npm run dev. I can see the index page on localhost:3000.
But npm run build gets:
% npm run build
> test#0.1.0 build /Users/minori/Documents/portfolio/test
> next build
info - Checking validity of types
Failed to compile.
./pages/index.js
8:7 Error: Missing "key" prop for element in array react/jsx-key
/*almost same messages repeated for every line*/
63:13 Error: Missing "key" prop for element in array react/jsx-key
info - Need to disable some ESLint rules? Learn more here: https://nextjs.org/docs/basic-features/eslint#disabling-rules
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! test#0.1.0 build: `next build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the test#0.1.0 build 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/minori/.npm/_logs/2022-02-25T17_53_21_317Z-debug.log
And here is the debug log:
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'run', 'build' ]
2 info using npm#6.14.15
3 info using node#v14.17.6
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle test#0.1.0~prebuild: test#0.1.0
6 info lifecycle test#0.1.0~build: test#0.1.0
7 verbose lifecycle test#0.1.0~build: unsafe-perm in lifecycle true
8 verbose lifecycle test#0.1.0~build: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/minori/Documents/portfolio/test/node_modules/.bin:/Users/minori/.npm-global/lib/node_modules/n/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Library/TeX/texbin:/opt/X11/bin:/Library/Apple/usr/bin:/Library/Frameworks/Mono.framework/Versions/Current/Commands:/Users/minori/bin:/opt/osxws/bin:/opt/osxws/sbin
9 verbose lifecycle test#0.1.0~build: CWD: /Users/minori/Documents/portfolio/test
10 silly lifecycle test#0.1.0~build: Args: [ '-c', 'next build' ]
11 silly lifecycle test#0.1.0~build: Returned: code: 1 signal: null
12 info lifecycle test#0.1.0~build: Failed to exec build script
13 verbose stack Error: test#0.1.0 build: `next build`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:400:28)
13 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:400:28)
13 verbose stack at maybeClose (internal/child_process.js:1055:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5)
14 verbose pkgid test#0.1.0
15 verbose cwd /Users/minori/Documents/portfolio/test
16 verbose Darwin 20.3.0
17 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "build"
18 verbose node v14.17.6
19 verbose npm v6.14.15
20 error code ELIFECYCLE
21 error errno 1
22 error test#0.1.0 build: `next build`
22 error Exit status 1
23 error Failed at the test#0.1.0 build script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
I already tried npm install -g npm-rm -rf node_modules-npm install, re-installing node.js, npm cache clear --force and rm package-lock.json.
Does anyone know what the problem is?
What else can I try now?
It's not you, there is an issue logged with eslint-plugin-react that create-next-app uses, if they haven't already done so (try npm create-next-app again) you can find eslint-plugin-react in your package.json to version 7.29.1
You can see the Vercel team noting the change and the eslint-plugin-react author's responding
https://github.com/yannickcr/eslint-plugin-react/issues/3215#issuecomment-1051115159
In my project, I'm using VueCli for the frontend. Now what I'm trying to do is deploy my project which is in remote server into the actual server. I'm using npm run build command to build the frontend first. But I can't build my project since the following error occurs again and again
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! mobile-h5#0.1.0 build: `vue-cli-service build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the mobile-h5#0.1.0 build 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/daisywu/.npm/_logs/2021-09-24T06_13_06_000Z-debug.log
I delete package-lock.json and node_modules,then do npm cache clean --force,then do npm install,Still unable to construct
debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'run', 'build' ]
2 info using npm#6.14.9
3 info using node#v14.15.3
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle mobile-h5#0.1.0~prebuild: mobile-h5#0.1.0
6 info lifecycle mobile-h5#0.1.0~build: mobile-h5#0.1.0
7 verbose lifecycle mobile-h5#0.1.0~build: unsafe-perm in lifecycle true
8 verbose lifecycle mobile-h5#0.1.0~build: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/daisywu/Documents/mobile-h5/node_modules/.bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
9 verbose lifecycle mobile-h5#0.1.0~build: CWD: /Users/daisywu/Documents/mobile-h5
10 silly lifecycle mobile-h5#0.1.0~build: Args: [ '-c', 'vue-cli-service build' ]
11 silly lifecycle mobile-h5#0.1.0~build: Returned: code: 1 signal: null
12 info lifecycle mobile-h5#0.1.0~build: Failed to exec build script
13 verbose stack Error: mobile-h5#0.1.0 build: `vue-cli-service build`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:315:20)
13 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:315:20)
13 verbose stack at maybeClose (internal/child_process.js:1048:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5)
14 verbose pkgid mobile-h5#0.1.0
15 verbose cwd /Users/daisywu/Documents/mobile-h5
16 verbose Darwin 20.3.0
17 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "build"
18 verbose node v14.15.3
19 verbose npm v6.14.9
20 error code ELIFECYCLE
21 error errno 1
22 error mobile-h5#0.1.0 build: `vue-cli-service build`
22 error Exit status 1
23 error Failed at the mobile-h5#0.1.0 build script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
Please help thank you
The reason is insufficient memory. Update the answer for your reference
Written in package.json
"build": "node --max_old_space_size=4096 node_modules/#vue/cli-service/bin/vue-cli-service.js build --mode development"
do npm run build
Trying to compile theme (named foo) in Prestashop:
cd themes/foo/_dev
npm run build
Get the following error.
npm ERR! code ELIFECYCLE
npm ERR! errno 2
npm ERR! prestashop-classic-dev-tools#1.0.0 build: `webpack`
npm ERR! Exit status 2
npm ERR!
npm ERR! Failed at the prestashop-classic-dev-tools#1.0.0 build 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! /root/.npm/_logs/2021-07-02T05_58_35_445Z-debug.log
Here is the log
0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'build' ]
2 info using npm#6.14.13
3 info using node#v14.17.0
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle prestashop-classic-dev-tools#1.0.0~prebuild: prestashop-classic-dev-tools#1.0.0
6 info lifecycle prestashop-classic-dev-tools#1.0.0~build: prestashop-classic-dev-tools#1.0.0
7 verbose lifecycle prestashop-classic-dev-tools#1.0.0~build: unsafe-perm in lifecycle true
8 verbose lifecycle prestashop-classic-dev-tools#1.0.0~build: PATH: /usr/lib/node_modules/npm/node_mod$
9 verbose lifecycle prestashop-classic-dev-tools#1.0.0~build: CWD: /var/www/html/themes/foo$
10 silly lifecycle prestashop-classic-dev-tools#1.0.0~build: Args: [ '-c', 'webpack' ]
11 silly lifecycle prestashop-classic-dev-tools#1.0.0~build: Returned: code: 2 signal: null
12 info lifecycle prestashop-classic-dev-tools#1.0.0~build: Failed to exec build script
13 verbose stack Error: prestashop-classic-dev-tools#1.0.0 build: `webpack`
13 verbose stack Exit status 2
13 verbose stack at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle$
13 verbose stack at EventEmitter.emit (events.js:376:20)
13 verbose stack at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle$
13 verbose stack at ChildProcess.emit (events.js:376:20)
13 verbose stack at maybeClose (internal/child_process.js:1055:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5)
14 verbose pkgid prestashop-classic-dev-tools#1.0.0
15 verbose cwd /var/www/html/themes/foo/_dev
16 verbose Linux 5.8.0-59-generic
17 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "build"
18 verbose node v14.17.0
19 verbose npm v6.14.13
20 error code ELIFECYCLE
21 error errno 2
22 error prestashop-classic-dev-tools#1.0.0 build: `webpack`
22 error Exit status 2
23 error Failed at the prestashop-classic-dev-tools#1.0.0 build script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 2, true ]
npm version is:
> npm -v
6.14.13
What could be the cause?
Cause of the issue not found. Resolved with the following commands:
Clean npm cache
> npm cache clean --force
Remove node modules
> rm -rf node_modules package-lock.json
Install npm
> npm install
Run build
> npm run build
I got error message 'not finished load plugins', when I trying to load local server with [npm run develop]
What should I do?
This is the error message I got:
not finished load plugins - 0.975s
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! Henisis#0.2.0 develop: `GATSBY_ENV=staging gatsby develop`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the Henisis#0.2.0 develop 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/mingyeongso/.npm/_logs/2020-04-08T06_51_49_655Z-debug.log
mingyeongui-MacBookPro:henesis-website mingyeongso$
From the debug file:
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'run', 'develop' ]
2 info using npm#6.14.2
3 info using node#v10.16.3
4 verbose run-script [ 'predevelop', 'develop', 'postdevelop' ]
5 info lifecycle Henisis#0.2.0~predevelop: Henisis#0.2.0
6 info lifecycle Henisis#0.2.0~develop: Henisis#0.2.0
7 verbose lifecycle Henisis#0.2.0~develop: unsafe-perm in lifecycle true
8 verbose lifecycle Henisis#0.2.0~develop: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/mingyeongso/Documents/GitHub/henesis-website/node_modules/.bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin
9 verbose lifecycle Henisis#0.2.0~develop: CWD: /Users/mingyeongso/Documents/GitHub/henesis-website
10 silly lifecycle Henisis#0.2.0~develop: Args: [ '-c', 'GATSBY_ENV=staging gatsby develop' ]
11 silly lifecycle Henisis#0.2.0~develop: Returned: code: 1 signal: null
12 info lifecycle Henisis#0.2.0~develop: Failed to exec develop script
13 verbose stack Error: Henisis#0.2.0 develop: GATSBY_ENV=staging gatsby develop
13 verbose stack Exit status 1
13 verbose stack at EventEmitter. (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:198:13)
13 verbose stack at ChildProcess. (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:198:13)
13 verbose stack at maybeClose (internal/child_process.js:982:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
14 verbose pkgid Henisis#0.2.0
15 verbose cwd /Users/mingyeongso/Documents/GitHub/henesis-website
16 verbose Darwin 18.7.0
17 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "develop"
18 verbose node v10.16.3
19 verbose npm v6.14.2
20 error code ELIFECYCLE
21 error errno 1
22 error Henisis#0.2.0 develop: GATSBY_ENV=staging gatsby develop
22 error Exit status 1
23 error Failed at the Henisis#0.2.0 develop script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
I resolved this error by this:
npm cache clean --force
delete package-lock.json file
npm install
I'm trying to run npm run test:unit and the true error seems to be test:unit: Failed to exec test:unit script from the npm debug.log. Yet the script DOES run and execute without issue.
I'm a little new to NPM + Node so I'm struggling with this behavior. When I run npm run test:unit ( "test:unit": "vue-cli-service test:unit" in Package.json) I get this output:
Test Suites: 1 passed, 1 total
Tests: 1 passed, 1 total
Snapshots: 1 file obsolete, 0 total
Time: 1.208s
Ran all test suites.
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! cheatsheet#0.1.0 test:unit: `vue-cli-service test:unit`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the cheatsheet#0.1.0 test:unit 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/max/.npm/_logs/2020-03-26T18_16_36_155Z-debug.log
Expected Result
The tests should just pass, I shouldn't see NPM/Node crash.
Running ./node_modules/.bin/vue-cli-service test:unit I get just the test and Jest output. Everything works as expected. So what is going wrong with my setup?
Attempted Resolution
reinstalled node_modules
updated npm
updated to node:stable
reinstall nvm (node version manager) and updated
attempted to add extra debug flags to vue-cli-service
npm_debug.log
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli '/home/max/.nvm/versions/node/v13.11.0/bin/node',
1 verbose cli '/home/max/.nvm/versions/node/v13.11.0/bin/npm',
1 verbose cli 'run',
1 verbose cli 'test:unit'
1 verbose cli ]
2 info using npm#6.14.4
3 info using node#v13.11.0
4 verbose run-script [ 'pretest:unit', 'test:unit', 'posttest:unit' ]
5 info lifecycle cheatsheet#0.1.0~pretest:unit: cheatsheet#0.1.0
6 info lifecycle cheatsheet#0.1.0~test:unit: cheatsheet#0.1.0
7 verbose lifecycle cheatsheet#0.1.0~test:unit: unsafe-perm in lifecycle true
8 verbose lifecycle cheatsheet#0.1.0~test:unit: PATH: /home/max/.nvm/versions/node/v13.11.0/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/max/cheatsheet_project/cheatsheet/node_modules/.bin:/home/max/.pyenv/plugins/pyenv-virtualenv/shims:/home/max/.pyenv/shims:~/.pyenv/bin:/home/max/Maven/apache-maven-3.5.2/bin:/home/max/.nvm/versions/node/v13.11.0/bin:/home/max/.rbenv/shims:/home/max/.rbenv/bin:/home/max/workspace/go/bin:/home/max/.cargo/bin:/home/max/.cargo/bin:/home/max/bin:/home/max/.local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:/usr/lib/jvm/java-9-oracle/bin:/usr/lib/jvm/java-9-oracle/db/bin:/usr/lib/jvm/java-9-oracle/bin:/usr/lib/jvm/java-9-oracle/db/bin:/usr/local/go/bin
9 verbose lifecycle cheatsheet#0.1.0~test:unit: CWD: /home/max/cheatsheet_project/cheatsheet
10 silly lifecycle cheatsheet#0.1.0~test:unit: Args: [ '-c', 'vue-cli-service test:unit' ]
11 silly lifecycle cheatsheet#0.1.0~test:unit: Returned: code: 1 signal: null
12 info lifecycle cheatsheet#0.1.0~test:unit: Failed to exec test:unit script
13 verbose stack Error: cheatsheet#0.1.0 test:unit: `vue-cli-service test:unit`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (/home/max/.nvm/versions/node/v13.11.0/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:315:20)
13 verbose stack at ChildProcess.<anonymous> (/home/max/.nvm/versions/node/v13.11.0/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:315:20)
13 verbose stack at maybeClose (internal/child_process.js:1026:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:286:5)
14 verbose pkgid cheatsheet#0.1.0
15 verbose cwd /home/max/cheatsheet_project/cheatsheet
16 verbose Linux 4.15.0-91-generic
17 verbose argv "/home/max/.nvm/versions/node/v13.11.0/bin/node" "/home/max/.nvm/versions/node/v13.11.0/bin/npm" "run" "test:unit"
18 verbose node v13.11.0
19 verbose npm v6.14.4
20 error code ELIFECYCLE
21 error errno 1
22 error cheatsheet#0.1.0 test:unit: `vue-cli-service test:unit`
22 error Exit status 1
23 error Failed at the cheatsheet#0.1.0 test:unit script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
./node_modules/.bin/vue-cli-service test:unit -u fixed this. This is the shorthand command for jest --updatesnapshot.
Since we just updated our component to point to a different address, it's reasonable to expect changes in the snapshot for this component. Our snapshot test case is failing because the snapshot for our updated component no longer matches the snapshot artifact for this test case.
To resolve this, we will need to update our snapshot artifacts. You can run Jest with a flag that will tell it to re-generate snapshots...
- From Snapshot Testing.
Observed the error about snapshots:
Snapshots: 1 file obsolete, 0 total
Unsure why this caused the NPM error but -u cleared it and I haven't seen it again.