-
Notifications
You must be signed in to change notification settings - Fork 5
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
ran npm install and one line change to readme to state tests are in docc
- Loading branch information
1 parent
ce794ff
commit 44fb607
Showing
3 changed files
with
48 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,45 @@ | ||
0 info it worked if it ends with ok | ||
1 verbose cli [ '/usr/local/Cellar/node/5.4.0/bin/node', | ||
1 verbose cli '/usr/local/bin/npm', | ||
1 verbose cli 'run', | ||
1 verbose cli 'test-las2json' ] | ||
2 info using [email protected] | ||
3 info using [email protected] | ||
4 verbose run-script [ 'pretest-las2json', 'test-las2json', 'posttest-las2json' ] | ||
5 info lifecycle [email protected]~pretest-las2json: [email protected] | ||
6 silly lifecycle [email protected]~pretest-las2json: no script for pretest-las2json, continuing | ||
7 info lifecycle [email protected]~test-las2json: [email protected] | ||
8 verbose lifecycle [email protected]~test-las2json: unsafe-perm in lifecycle true | ||
9 verbose lifecycle [email protected]~test-las2json: PATH: /usr/local/lib/node_modules/npm/bin/node-gyp-bin:/Users/justingosses/Code/wellio.js/node_modules/.bin:/Users/justingosses/.gem/ruby/3.0.1p64/bin:/usr/local/opt/ruby/bin:/usr/local/lib/ruby/gems/3.0.0/bin:/Users/justingosses/google-cloud-sdk/bin:/Users/justingosses/anaconda/bin:/Users/justingosses/:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/Applications/Postgres.app/Contents/Versions/latest/bin | ||
10 verbose lifecycle [email protected]~test-las2json: CWD: /Users/justingosses/Code/wellio.js | ||
11 silly lifecycle [email protected]~test-las2json: Args: [ '-c', 'tape dist/test/las2json/test_*.js' ] | ||
12 info lifecycle [email protected]~test-las2json: Failed to exec test-las2json script | ||
13 verbose stack Error: [email protected] test-las2json: `tape dist/test/las2json/test_*.js` | ||
13 verbose stack spawn ENOENT | ||
13 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:17:16) | ||
13 verbose stack at emitTwo (events.js:87:13) | ||
13 verbose stack at ChildProcess.emit (events.js:172:7) | ||
13 verbose stack at maybeClose (internal/child_process.js:821:16) | ||
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5) | ||
14 verbose pkgid [email protected] | ||
15 verbose cwd /Users/justingosses/Code/wellio.js/dist | ||
16 error Darwin 17.7.0 | ||
17 error argv "/usr/local/Cellar/node/5.4.0/bin/node" "/usr/local/bin/npm" "run" "test-las2json" | ||
18 error node v5.4.0 | ||
19 error npm v3.3.12 | ||
20 error file sh | ||
21 error code ELIFECYCLE | ||
22 error errno ENOENT | ||
23 error syscall spawn | ||
24 error [email protected] test-las2json: `tape dist/test/las2json/test_*.js` | ||
24 error spawn ENOENT | ||
25 error Failed at the [email protected] test-las2json script 'tape dist/test/las2json/test_*.js'. | ||
25 error Make sure you have the latest version of node.js and npm installed. | ||
25 error If you do, this is most likely a problem with the wellio package, | ||
25 error not with npm itself. | ||
25 error Tell the author that this fails on your system: | ||
25 error tape dist/test/las2json/test_*.js | ||
25 error You can get their info via: | ||
25 error npm owner ls wellio | ||
25 error There is likely additional logging output above. | ||
26 verbose exit [ 1, true ] |
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.