Cat npm-debug.logs on failure

[doug-wade]

#280 and #294 are plagued by failures that I can't repro locally. Dump every npm-debug.log in the monorepo to stdout so they're available in the travis logs.

[doug-wade]

Here's a build that includes the result https://travis-ci.org/redfin/react-server/builds/139049381

The relevant part of the log is

Errored while running npm script 'test' in 'react-server-gulp-module-tagger'
Error: Command failed: npm run test 
(node:4100) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
npm ERR! Linux 3.13.0-40-generic
npm ERR! argv "/home/travis/.nvm/versions/node/v6.2.2/bin/node" "/home/travis/.nvm/versions/node/v6.2.2/bin/npm" "run" "test"
npm ERR! node v6.2.2
npm ERR! npm  v3.9.5
npm ERR! code ELIFECYCLE
npm ERR! [email protected] test: `gulp test`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] test script 'gulp test'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the react-server-gulp-module-tagger package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     gulp test
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs react-server-gulp-module-tagger
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls react-server-gulp-module-tagger
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /home/travis/build/redfin/react-server/packages/react-server-gulp-module-tagger/npm-debug.log
    at ChildProcess.exithandler (child_process.js:207:12)
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:191:7)
    at maybeClose (internal/child_process.js:852:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:215:5)
Errored while running RunCommand.execute
Error: Command failed: npm run test 
(node:4100) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
npm ERR! Linux 3.13.0-40-generic
npm ERR! argv "/home/travis/.nvm/versions/node/v6.2.2/bin/node" "/home/travis/.nvm/versions/node/v6.2.2/bin/npm" "run" "test"
npm ERR! node v6.2.2
npm ERR! npm  v3.9.5
npm ERR! code ELIFECYCLE
npm ERR! [email protected] test: `gulp test`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] test script 'gulp test'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the react-server-gulp-module-tagger package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     gulp test
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs react-server-gulp-module-tagger
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls react-server-gulp-module-tagger
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /home/travis/build/redfin/react-server/packages/react-server-gulp-module-tagger/npm-debug.log
    at ChildProcess.exithandler (child_process.js:207:12)
    at emitTwo (events.js:106:13)
    at ChildProcess.emit (events.js:191:7)
    at maybeClose (internal/child_process.js:852:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:215:5)
npm ERR! Test failed.  See above for more details.
The command "npm test" exited with 1.
after_failure
0.97s$ npm run debug
> @ debug /home/travis/build/redfin/react-server
> for d in packages/*/npm-debug.log*; do echo $d; cat $d; done
packages/react-server-gulp-module-tagger/npm-debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/home/travis/.nvm/versions/node/v6.2.2/bin/node',
1 verbose cli   '/home/travis/.nvm/versions/node/v6.2.2/bin/npm',
1 verbose cli   'run',
1 verbose cli   'test' ]
2 info using [email protected]
3 info using [email protected]
4 verbose run-script [ 'pretest', 'test', 'posttest' ]
5 info lifecycle [email protected]~pretest: [email protected]
6 silly lifecycle [email protected]~pretest: no script for pretest, continuing
7 info lifecycle [email protected]~test: [email protected]
8 verbose lifecycle [email protected]~test: unsafe-perm in lifecycle true
9 verbose lifecycle [email protected]~test: PATH: /home/travis/.nvm/versions/node/v6.2.2/lib/node_modules/npm/bin/node-gyp-bin:/home/travis/build/redfin/react-server/packages/react-server-gulp-module-tagger/node_modules/.bin:/home/travis/.nvm/versions/node/v6.2.2/bin:/home/travis/.nvm/versions/node/v6.2.2/lib/node_modules/npm/bin/node-gyp-bin:/home/travis/build/redfin/react-server/node_modules/.bin:/home/travis/.nvm/versions/node/v6.2.2/bin:/home/travis/.nvm/versions/node/v6.2.2/bin:/home/travis/bin:/home/travis/.local/bin:/home/travis/.gimme/versions/go1.4.1.linux.amd64/bin:/usr/local/phantomjs/bin:./node_modules/.bin:/usr/local/maven-3.2.5/bin:/usr/local/clang-3.4/bin:/home/travis/.gimme/versions/go1.4.1.linux.amd64/bin:/usr/local/phantomjs/bin:./node_modules/.bin:/usr/local/maven-3.2.5/bin:/usr/local/clang-3.4/bin:/home/travis/.gimme/versions/go1.4.1.linux.amd64/bin:/home/travis/.rvm/gems/ruby-1.9.3-p551/bin:/home/travis/.rvm/gems/ruby-1.9.3-p551@global/bin:/home/travis/.rvm/rubies/ruby-1.9.3-p551/bin:/usr/local/phantomjs/bin:./node_modules/.bin:/usr/local/maven-3.2.5/bin:/usr/local/clang-3.4/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/home/travis/.rvm/bin:/home/travis/.rvm/bin:/home/travis/.rvm/bin
10 verbose lifecycle [email protected]~test: CWD: /home/travis/build/redfin/react-server/packages/react-server-gulp-module-tagger
11 silly lifecycle [email protected]~test: Args: [ '-c', 'gulp test' ]
12 silly lifecycle [email protected]~test: Returned: code: 1  signal: null
13 info lifecycle [email protected]~test: Failed to exec test script
14 verbose stack Error: [email protected] test: `gulp test`
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter.<anonymous> (/home/travis/.nvm/versions/node/v6.2.2/lib/node_modules/npm/lib/utils/lifecycle.js:245:16)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at EventEmitter.emit (events.js:191:7)
14 verbose stack     at ChildProcess.<anonymous> (/home/travis/.nvm/versions/node/v6.2.2/lib/node_modules/npm/lib/utils/spawn.js:24:14)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at ChildProcess.emit (events.js:191:7)
14 verbose stack     at maybeClose (internal/child_process.js:852:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:215:5)
15 verbose pkgid [email protected]
16 verbose cwd /home/travis/build/redfin/react-server/packages/react-server-gulp-module-tagger
17 error Linux 3.13.0-40-generic
18 error argv "/home/travis/.nvm/versions/node/v6.2.2/bin/node" "/home/travis/.nvm/versions/node/v6.2.2/bin/npm" "run" "test"
19 error node v6.2.2
20 error npm  v3.9.5
21 error code ELIFECYCLE
22 error [email protected] test: `gulp test`
22 error Exit status 1
23 error Failed at the [email protected] test script 'gulp test'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the react-server-gulp-module-tagger package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error     gulp test
23 error You can get information on how to open an issue for this project with:
23 error     npm bugs react-server-gulp-module-tagger
23 error Or if that isn't available, you can get their info via:
23 error     npm owner ls react-server-gulp-module-tagger
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]
Done. Your build exited with 1.

[gigabo]

Awesome.