Ever since 3.0.0 running mocha tests in my project crashes on startup with an error 0xC0000005 #2697

Activity

1. ChALkeR

   added

   windowsIssues and PRs related to the Windows platform.Issues and PRs related to the Windows platform.

   on Sep 5, 2015
2. capaj commented on Sep 5, 2015

   

   capaj

   on Sep 5, 2015

   Author

   More actions

   Also fails with latest node 4.0.0-rc.1
3. targos commented on Sep 5, 2015

   

   targos

   on Sep 5, 2015

   Member

   More actions

   Do you have any idea about what part of your test suite is making it crash?
   I briefly tried to run it on my mac but couldn't because I don't have MongoDB.
4. rvagg commented on Sep 5, 2015

   

   rvagg

   on Sep 5, 2015

   Member

   More actions

   > moonridge@0.9.1 test /home/rvagg/Moonridge
   > mocha
   
   module.js:338
       throw err;
       ^
   
   Error: Cannot find module '../../Moonridge-client/moonridge-client'
       at Function.Module._resolveFilename (module.js:336:15)
       at Function.Module._load (module.js:286:25)
       at Module.require (module.js:365:17)
       at require (module.js:384:17)
       at Object.<anonymous> (/home/rvagg/Moonridge/test/utils/run_server_client.js:5:11)
       at Module._compile (module.js:434:26)
       at Object.Module._extensions..js (module.js:452:10)
       at Module.load (module.js:355:32)
       at Function.Module._load (module.js:310:12)
       at Module.require (module.js:365:17)
       at require (module.js:384:17)
       at Object.<anonymous> (/home/rvagg/Moonridge/test/basic-CRUD.spec.js:3:14)
       at Module._compile (module.js:434:26)
       at Object.Module._extensions..js (module.js:452:10)
       at Module.load (module.js:355:32)
       at Function.Module._load (module.js:310:12)
       at Module.require (module.js:365:17)
       at require (module.js:384:17)
       at /home/rvagg/Moonridge/node_modules/mocha/lib/mocha.js:216:27
       at Array.forEach (native)
       at Mocha.loadFiles (/home/rvagg/Moonridge/node_modules/mocha/lib/mocha.js:213:14)
       at Mocha.run (/home/rvagg/Moonridge/node_modules/mocha/lib/mocha.js:453:10)
       at Object.<anonymous> (/home/rvagg/Moonridge/node_modules/mocha/bin/_mocha:401:18)
       at Module._compile (module.js:434:26)
       at Object.Module._extensions..js (module.js:452:10)
       at Module.load (module.js:355:32)
       at Function.Module._load (module.js:310:12)
       at Function.Module.runMain (module.js:475:10)
       at startup (node.js:117:18)
       at node.js:951:3
   npm ERR! Test failed.  See above for more details.
   rvagg@rvagg:~/Moonridge$ module.js:338
       throw err;
       ^
   
   Error: Cannot find module './Moonridge-client/moonridge/moonridge-method-validations'
       at Function.Module._resolveFilename (module.js:336:15)
       at Function.Module._load (module.js:286:25)
       at Module.require (module.js:365:17)
       at require (module.js:384:17)
       at Object.<anonymous> (/home/rvagg/Moonridge/query-builder.js:2:33)
       at Module._compile (module.js:434:26)
       at Object.Module._extensions..js (module.js:452:10)
       at Module.load (module.js:355:32)
       at Function.Module._load (module.js:310:12)
       at Module.require (module.js:365:17)
       at require (module.js:384:17)
   

   wut?

   also, it doesn't cleanly npm install because there are addons in the dependency tree that need to be updated for v3+ which is probably why it's not set up properly

   @capaj if you rm -rf node_modules and npm install how far do you get? seems to be that this is all about not having dependencies that are compatible.
5. capaj commented on Sep 5, 2015

   

   capaj

   on Sep 5, 2015

   Author

   More actions

   @rvagg yes, npm 3 gets stuck on downloading a git submodule. Is this not supported anymore by NPM?

   Specifically the last npm command when running npm i --verbose is:

   npm verb resolveHead git+https://github.com/capaj/socket.io-rpc-event-handlers.g
   it resolved Git URL: git+https://github.com/capaj/socket.io-rpc-event-handlers.g
   it#3bd44bbe6b6606cfaed9686542663a1d300d0e86
   
6. ChALkeR

   removed

   windowsIssues and PRs related to the Windows platform.Issues and PRs related to the Windows platform.

   on Sep 5, 2015
7. capaj commented on Sep 5, 2015

   

   capaj

   on Sep 5, 2015

   Author

   More actions

   @rvagg oh there was a git submodule I forgot to mention. So you would have to do a recursive clone.

   Also I have tried from a scratch on my windows machine with npm 3.3.2 and Node 4.0.0-rc.1 and it works. Tests run as before. @targos I guess this was some problem with my npm dependencies. Glad it is resolved now.
8. capaj

   closed this as completedon Sep 5, 2015