Created
June 17, 2017 05:57
-
-
Save desmond-dsouza/3d3e86685f8e044c3851b3bdf33fc479 to your computer and use it in GitHub Desktop.
Debug Log from build failure with bs-platform 1.7.5 on bucklescript-tea project
This file contains hidden or 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
| more /Users/desmond/.npm/_logs/2017-06-17T05_48_29_953Z-debug.log | |
| 0 info it worked if it ends with ok | |
| 1 verbose cli [ '/usr/local/Cellar/node/7.10.0/bin/node', | |
| 1 verbose cli '/usr/local/bin/npm', | |
| 1 verbose cli 'run', | |
| 1 verbose cli 'build' ] | |
| 2 info using npm@4.2.0 | |
| 3 info using node@v7.10.0 | |
| 4 verbose run-script [ 'prebuild', 'build', 'postbuild' ] | |
| 5 info lifecycle interactive-pictures@0.0.0~prebuild: interactive-pictures@0.0.0 | |
| 6 silly lifecycle interactive-pictures@0.0.0~prebuild: no script for prebuild, continuing | |
| 7 info lifecycle interactive-pictures@0.0.0~build: interactive-pictures@0.0.0 | |
| 8 verbose lifecycle interactive-pictures@0.0.0~build: unsafe-perm in lifecycle true | |
| 9 verbose lifecycle interactive-pictures@0.0.0~build: PATH: /usr/local/lib/node_modules/npm/bin/node-gyp-bin:/Users/desmond/Documents/code/code-reason/interactive-pictures/node_modules/.bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/local/share/dotnet:/Users/desmond/anaconda3/bin:/Users/desmond/bin:/usr/local/heroku/bin:/usr/local/go/bin:/Applications/Postgres.app/Contents/Versions/latest/bin:/Users/desmond/.local/bin | |
| 10 verbose lifecycle interactive-pictures@0.0.0~build: CWD: /Users/desmond/Documents/code/code-reason/interactive-pictures | |
| 11 silly lifecycle interactive-pictures@0.0.0~build: Args: [ '-c', 'npm-run-all build:*' ] | |
| 12 silly lifecycle interactive-pictures@0.0.0~build: Returned: code: 1 signal: null | |
| 13 info lifecycle interactive-pictures@0.0.0~build: Failed to exec build script | |
| 14 verbose stack Error: interactive-pictures@0.0.0 build: `npm-run-all build:*` | |
| 14 verbose stack Exit status 1 | |
| 14 verbose stack at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:279:16) | |
| 14 verbose stack at emitTwo (events.js:106:13) | |
| 14 verbose stack at EventEmitter.emit (events.js:194:7) | |
| 14 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/spawn.js:40:14) | |
| 14 verbose stack at emitTwo (events.js:106:13) | |
| 14 verbose stack at ChildProcess.emit (events.js:194:7) | |
| 14 verbose stack at maybeClose (internal/child_process.js:899:16) | |
| 14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5) | |
| 15 verbose pkgid interactive-pictures@0.0.0 | |
| 16 verbose cwd /Users/desmond/Documents/code/code-reason/interactive-pictures | |
| 17 error Darwin 15.6.0 | |
| 18 error argv "/usr/local/Cellar/node/7.10.0/bin/node" "/usr/local/bin/npm" "run" "build" | |
| 19 error node v7.10.0 | |
| 20 error npm v4.2.0 | |
| 21 error code ELIFECYCLE | |
| 22 error errno 1 | |
| 23 error interactive-pictures@0.0.0 build: `npm-run-all build:*` | |
| 23 error Exit status 1 | |
| 24 error Failed at the interactive-pictures@0.0.0 build script 'npm-run-all build:*'. | |
| 24 error Make sure you have the latest version of node.js and npm installed. | |
| 24 error If you do, this is most likely a problem with the interactive-pictures package, | |
| 24 error not with npm itself. | |
| 24 error Tell the author that this fails on your system: | |
| 24 error npm-run-all build:* | |
| 24 error You can get information on how to open an issue for this project with: | |
| 24 error npm bugs interactive-pictures | |
| 24 error Or if that isn't available, you can get their info via: | |
| 24 error npm owner ls interactive-pictures | |
| 24 error There is likely additional logging output above. | |
| 25 verbose exit [ 1, true ] |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment