6
Ho un problema quando eseguo gulp mentre si uccide durante l'attività. Io non sto facendo nulla:gulp viene ucciso irregolarmente
> gulp build
[11:25:34] Using gulpfile /app/app-base/frontend/gulpfile.js
[11:25:34] Starting 'css-clean'...
[11:25:34] Starting 'js-clean'...
[11:25:34] Finished 'css-clean' after 5.99 ms
[11:25:34] Starting 'css-build'...
[11:25:34] Finished 'js-clean' after 17 ms
[11:25:34] Starting 'js-build'...
[11:25:35] Finished 'css-build' after 888 ms
[11:25:35] Starting 'css'...
[11:25:35] Finished 'css' after 13 μs
Killed
npm ERR! [email protected] build: `gulp build`
npm ERR! Exit status 137
npm ERR!
npm ERR! Failed at the [email protected] build script.
npm ERR! This is most likely a problem with the app-frontend package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! gulp build
npm ERR! You can get their info via:
npm ERR! npm owner ls app-frontend
npm ERR! There is likely additional logging output above.
npm ERR! System Linux 3.13.0-43-generic
npm ERR! command "/root/.nvm/v0.10.35/bin/node" "/root/.nvm/v0.10.35/bin/npm" "run" "build"
npm ERR! cwd /app/app-base/frontend
npm ERR! node -v v0.10.35
npm ERR! npm -v 1.4.28
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /app/app-base/frontend/npm-debug.log
npm ERR! not ok code 0
Questo è il mio compito js-build che sembrano essere la causa di esso:
gulp.task('js-build', ['js-clean'], function() {
return gulp
.src(PATHS.js.input)
.pipe(plumber())
.pipe(browserify({
transform: [
'reactify',
'envify',
],
}))
.pipe(rename(PATHS.js.outputFile))
.pipe(uglify())
.pipe(gulp.dest(PATHS.js.output));
});
che funzionerà più spesso se rimuovere uglify ma doesn' t lavorare al 100%. Potrebbe essere correlato al tempo necessario, sembra essere correlato a quello.
Ecco il NPM-debug.log:
1 0 info it worked if it ends with ok
2 1 verbose cli [ '/root/.nvm/v0.10.35/bin/node',
3 1 verbose cli '/root/.nvm/v0.10.35/bin/npm',
4 1 verbose cli 'start' ]
5 2 info using [email protected]
6 3 info using [email protected]
7 4 verbose run-script [ 'prestart', 'start', 'poststart' ]
8 5 info prestart [email protected]
9 6 info start [email protected]
10 7 verbose unsafe-perm in lifecycle true
11 8 info [email protected] Failed to exec start script
12 9 error [email protected] start: `./scripts/start.sh`
13 9 error Exit status 1
14 10 error Failed at the [email protected] start script.
15 10 error This is most likely a problem with the app-base package,
16 10 error not with npm itself.
17 10 error Tell the author that this fails on your system:
18 10 error ./scripts/start.sh
19 10 error You can get their info via:
20 10 error npm owner ls app-base
21 10 error There is likely additional logging output above.
22 11 error System Linux 3.13.0-43-generic
23 12 error command "/root/.nvm/v0.10.35/bin/node" "/root/.nvm/v0.10.35/bin/npm" "start"
24 13 error cwd /app/app-base
25 14 error node -v v0.10.35
26 15 error npm -v 1.4.28
27 16 error code ELIFECYCLE
28 17 verbose exit [ 1, true ]
Condividi questo .... - '/ app/app-base/frontend/npm-debug.log' –
Non dice niente di più di quello che dice il log della console, ma sicuro. Dammi un secondo ... –
aggiunto il file nom-debug.log. –