Skip to content
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.

Followed the instructions for building and running tests but tests fail #195

Closed
lee-dohm opened this issue Sep 20, 2014 · 4 comments
Closed

Comments

@lee-dohm
Copy link
Contributor

Specifically:

  • Clone the repository
  • Run npm install
  • Run grunt to compile the CoffeeScript code
  • Run npm test to run the specs

Output is:

$ npm test

> atom-package-manager@0.96.0 test /Volumes/Data/Users/Lee/Source/apm
> grunt test

Running "clean" task

Running "coffee:glob_to_multiple" (coffee) task

Running "coffeelint:src" (coffeelint) task
>> 37 files lint free.

Running "coffeelint:test" (coffeelint) task
>> 17 files lint free.

Running "shell:test" (shell) task
dyld: lazy symbol binding failed: Symbol not found: _node_module_register
  Referenced from: /Volumes/Data/Users/Lee/Source/apm/node_modules/keytar/build/Release/keytar.node
  Expected in: dynamic lookup

dyld: Symbol not found: _node_module_register
  Referenced from: /Volumes/Data/Users/Lee/Source/apm/node_modules/keytar/build/Release/keytar.node
  Expected in: dynamic lookup

Warning: Command failed: dyld: lazy symbol binding failed: Symbol not found: _node_module_register
  Referenced from: /Volumes/Data/Users/Lee/Source/apm/node_modules/keytar/build/Release/keytar.node
  Expected in: dynamic lookup

dyld: Symbol not found: _node_module_register
  Referenced from: /Volumes/Data/Users/Lee/Source/apm/node_modules/keytar/build/Release/keytar.node
  Expected in: dynamic lookup

 Use --force to continue.

Aborted due to warnings.
npm ERR! Test failed.  See above for more details.
npm ERR! not ok code 0

Ideas?

@kevinsawicki
Copy link
Contributor

What version of node are you using?

@lee-dohm
Copy link
Contributor Author

$ npm --version
1.4.9
$ node --version
v0.10.28

I suppose this isn't the same as I should be running?

@kevinsawicki
Copy link
Contributor

No, that version looks good for both, I'm on npm 1.4.4 and node 0.10.32 which is pretty similar.

I just thought this was some old node 0.11 problem, and after some googling, it looks like it was, Level/levelup#240

Did you ever build apm before using node 0.11? Does removing node_modules and rebuilding get you any further?

@lee-dohm
Copy link
Contributor Author

I thought it was a brand new clone, but yes ... I just wiped the node_modules directory and reran the build and the tests pass now. Thanks!

As part of my planned pull requests, I'll submit another one that adds this tidbit of troubleshooting to the build part of the README.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants