Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

error testing npm #3369

Closed
aeosynth opened this Issue Apr 23, 2013 · 6 comments

Comments

Projects
None yet
5 participants

osx 10.7.5, node v0.10.4, npm 1.2.18

on a fresh clone:

$ npm test

> npm@1.2.18 test /Users/james/src/forks/npm
> node ./test/run.js && tap test/tap/*.js

# testing in /var/folders/0c/0sx_4mpn527c_x325rhbyj5h0000gn/T/npm-test-2751
# global prefix = /var/folders/0c/0sx_4mpn527c_x325rhbyj5h0000gn/T/npm-test-2751/root

+node "/Users/james/src/forks/npm/bin/npm-cli.js" install "/Users/james/src/forks/npm"
 1> > npm@1.2.18 prepublish /Users/james/src/forks/npm
 1> > node bin/npm-cli.js prune ; rm -rf test/*/*/node_modules ; make -j4 doc
 1> 
 1> scripts/doc-build.sh doc/api/help-search.md man/man3/help-search.3
 1> scripts/doc-build.sh doc/api/init.md man/man3/init.3
 1> scripts/doc-build.sh doc/api/install.md man/man3/install.3
 1> scripts/doc-build.sh doc/api/link.md man/man3/link.3
 1> node cli.js install ronn
 1> /var/folders/0c/0sx_4mpn527c_x325rhbyj5h0000gn/T/npm-test-2751/root/bin/ronn -> /var/folders/0c/0sx_4mpn527c_x325rhbyj5h0000gn/T/npm-test-2751/root/lib/node_modules/ronn/bin/ronn.js
 1> ronn@0.4.0 /var/folders/0c/0sx_4mpn527c_x325rhbyj5h0000gn/T/npm-test-2751/root/lib/node_modules/ronn
 1> ├── opts@1.2.2
 1> └── markdown@0.4.0 (nopt@1.0.10)
 2> npm http GET https://registry.npmjs.org/ronn
 2> npm http 304 https://registry.npmjs.org/ronn
 2> npm http GET https://registry.npmjs.org/opts
 2> npm http GET https://registry.npmjs.org/markdown
 2> npm http 304 https://registry.npmjs.org/opts
 2> npm http 304 https://registry.npmjs.org/markdown
 2> npm http GET https://registry.npmjs.org/nopt
 2> npm http 304 https://registry.npmjs.org/nopt
 2> npm http GET https://registry.npmjs.org/abbrev
 2> npm http 304 https://registry.npmjs.org/abbrev
 2> scripts/doc-build.sh: line 45: ./node_modules/.bin/ronn: No such file or directory
 2> make: *** [man/man3/help-search.3] Error 1
 2> make: *** Waiting for unfinished jobs....
 2> scripts/doc-build.sh: line 45: ./node_modules/.bin/ronn: No such file or directory
 2> make: *** [man/man3/link.3] Error 1
 2> scripts/doc-build.sh: line 45: ./node_modules/.bin/ronn: No such file or directory
 2> scripts/doc-build.sh: line 45: ./node_modules/.bin/ronn: No such file or directory
 2> make: *** [man/man3/init.3] Error 1
 2> make: *** [man/man3/install.3] Error 1
 2> npm ERR! addLocalDirectory Could not pack "/Users/james/src/forks/npm" to "/var/folders/0c/0sx_4mpn527c_x325rhbyj5h0000gn/T/npm-2752/1366674884259-0.8273566085845232/tmp.tgz"
 2> npm ERR! addLocal Could not install /Users/james/src/forks/npm
 2> npm ERR! npm@1.2.18 prepublish: `node bin/npm-cli.js prune ; rm -rf test/*/*/node_modules ; make -j4 doc`
 2> npm ERR! `sh "-c" "node bin/npm-cli.js prune ; rm -rf test/*/*/node_modules ; make -j4 doc"` failed with 2
 2> npm ERR! 
 2> npm ERR! Failed at the npm@1.2.18 prepublish script.
 2> npm ERR! This is most likely a problem with the npm package,
 2> npm ERR! not with npm itself.
 2> npm ERR! Tell the author that this fails on your system:
 2> npm ERR!     node bin/npm-cli.js prune ; rm -rf test/*/*/node_modules ; make -j4 doc
 2> npm ERR! You can get their info via:
 2> npm ERR!     npm owner ls npm
 2> npm ERR! There is likely additional logging output above.
 2> 
 2> npm ERR! System Darwin 11.4.2
 2> npm ERR! command "/usr/local/Cellar/node/0.10.4/bin/node" "/Users/james/src/forks/npm/bin/npm-cli.js" "install" "/Users/james/src/forks/npm"
 2> npm ERR! cwd /Users/james/src/forks/npm/test
 2> npm ERR! node -v v0.10.4
 2> npm ERR! npm -v 1.2.18
 2> npm ERR! code ELIFECYCLE
 2> npm ERR! 
 2> npm ERR! Additional logging details can be found in:
 2> npm ERR!     /Users/james/src/forks/npm/test/npm-debug.log
 2> npm ERR! not ok code 0
 2> 
not ok 1 node "/Users/james/src/forks/npm/bin/npm-cli.js" install "/Users/james/src/forks/npm"
1..1

/Users/james/src/forks/npm/test/run.js:226
  if (er) throw er
                ^
Error: failed node "/Users/james/src/forks/npm/bin/npm-cli.js" install "/Users/james/src/forks/npm"
    at /Users/james/src/forks/npm/test/run.js:99:10
    at ChildProcess.exithandler (child_process.js:636:7)
    at ChildProcess.EventEmitter.emit (events.js:98:17)
    at maybeClose (child_process.js:730:16)
    at Process.ChildProcess._handle.onexit (child_process.js:797:5)
npm ERR! Test failed.  See above for more details.
npm ERR! not ok code 0

manually running the failing command - node bin/npm-cli.js prune ; rm -rf test/*/*/node_modules ; make -j4 doc - worked, but i encountered another error:

+npm test npm-test-peer-deps
 1> > npm-test-peer-deps@0.0.0 test /Users/james/src/forks/npm/npm-test-7753/root/lib/node_modules/npm-test-peer-deps
 1> > node test.js
 2> /Users/james/src/forks/npm/npm-test-7753/root/lib/node_modules/npm-test-peer-deps/test.js:14
 2>   if (err) throw err
 2>                  ^
 2> Error: Command failed: npm ERR! max depth reached: opener@1.3.0, required by npm-test-peer-deps-file@1.2.3
 2> npm ERR! not ok code 0
 2> 
 2>     at ChildProcess.exithandler (child_process.js:632:15)
 2>     at ChildProcess.EventEmitter.emit (events.js:98:17)
 2>     at maybeClose (child_process.js:730:16)
 2>     at Process.ChildProcess._handle.onexit (child_process.js:797:5)
 2> npm ERR! Test failed.  See above for more details.
 2> npm ERR! not ok code 0
 2> 
not ok 33 npm test npm-test-peer-deps
1..33

/Users/james/src/forks/npm/test/run.js:226
  if (er) throw er
                ^
Error: failed npm test npm-test-peer-deps
    at /Users/james/src/forks/npm/test/run.js:99:10
    at ChildProcess.exithandler (child_process.js:636:7)
    at ChildProcess.EventEmitter.emit (events.js:98:17)
    at maybeClose (child_process.js:730:16)
    at Process.ChildProcess._handle.onexit (child_process.js:797:5)
npm ERR! Test failed.  See above for more details.
npm ERR! not ok code 0
Contributor

luk- commented Aug 17, 2013

Please try latest.

fails on npm-test-peer-deps (osx 10.7.5, node 0.10.16, npm 1.3.8):

$ npm test

> npm@1.3.8 test /Users/james/src/clone/npm
> node ./test/run.js && tap test/tap/*.js

# testing in /var/folders/0c/0sx_4mpn527c_x325rhbyj5h0000gn/T/npm-test-23339
# global prefix = /var/folders/0c/0sx_4mpn527c_x325rhbyj5h0000gn/T/npm-test-23339/root

...

+npm test npm-test-peer-deps
 1> > npm-test-peer-deps@0.0.0 test /var/folders/0c/0sx_4mpn527c_x325rhbyj5h0000gn/T/npm-test-23339/root/lib/node_modules/npm-test-peer-deps
 1> > node test.js
 2> /private/var/folders/0c/0sx_4mpn527c_x325rhbyj5h0000gn/T/npm-test-23339/root/lib/node_modules/npm-test-peer-deps/test.js:14
 2>   if (err) throw err
 2>                  ^
 2> Error: Command failed: npm ERR! max depth reached: opener@1.3.0, required by npm-test-peer-deps-file@1.2.3
 2> npm ERR! not ok code 0
 2> 
 2>     at ChildProcess.exithandler (child_process.js:637:15)
 2>     at ChildProcess.EventEmitter.emit (events.js:98:17)
 2>     at maybeClose (child_process.js:735:16)
 2>     at Process.ChildProcess._handle.onexit (child_process.js:802:5)
 2> npm ERR! weird error 8
 2> npm ERR! not ok code 0
 2> 
not ok 33 npm test npm-test-peer-deps
1..33

/Users/james/src/clone/npm/test/run.js:226
  if (er) throw er
                ^
Error: failed npm test npm-test-peer-deps
    at /Users/james/src/clone/npm/test/run.js:99:10
    at ChildProcess.exithandler (child_process.js:641:7)
    at ChildProcess.EventEmitter.emit (events.js:98:17)
    at maybeClose (child_process.js:735:16)
    at Process.ChildProcess._handle.onexit (child_process.js:802:5)
npm ERR! weird error 8
npm ERR! not ok code 0
Member

robertkowalski commented Nov 9, 2013

Sorry, but I am not able to reproduce this.

aeosynth commented Dec 2, 2013

This was caused by my .npmrc configuration; setting depth = 1 triggers this error. Hopefully fixed with #2843.

on Ubunut of digital Ocean and I met this problem

root@kewinDO:~# nodejs  --version    
v0.10.25
root@kewinDO:~# npm -v
1.3.10
root@kewinDO:~# npm ls -g --depth=0
/usr/local/lib
├── async@0.9.0
├── bower@1.3.9
├── grunt@0.4.5
├── redis@0.12.1
├── slap@0.0.32
└── socket.io@1.0.6

npm ERR! max depth reached: async@0.9.0, required by undefined@undefined
npm ERR! max depth reached: bower@1.3.9, required by undefined@undefined
npm ERR! max depth reached: grunt@0.4.5, required by undefined@undefined
npm ERR! max depth reached: redis@0.12.1, required by undefined@undefined
npm ERR! max depth reached: slap@0.0.32, required by undefined@undefined
npm ERR! max depth reached: socket.io@1.0.6, required by undefined@undefined
npm ERR! not ok code 0

Contributor

othiym23 commented Aug 28, 2014

The npm team no longer supports versions of npm 1.3.x and older. Either upgrade your version of npm to the latest stable version using sudo npm -g install npm@latest or upgrade your whole Node installation to use NodeSource's PPA.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment