npm/npm — pull request #4663 by robertkowalski (2014-02-12 19:51:44+00:00)
Title: skip failing test on linux

The GNU shell returns a code and no signal if it gets a SIGSEGV
signal, so we have to skip this. Hat tip to @tjfontaine

This test fails on Linux and therefore travis. I first thought it would be a node code issue and created some test-code (https://github.com/robertkowalski/node-signal-debian), but happily TJ helped me to identify the issue with https://github.com/npm/npm/blob/9e12b1a174bcbcebb26732016cd1961a93947751/lib/utils/lifecycle.js#L207:

```
19:29:27 <@tjfontaine> robertkowalski: ok, I can explain what's going on here
19:29:34 <@tjfontaine> robertkowalski: we both just made the same mistake
19:29:54 <@tjfontaine> robertkowalski: the exit code and signal you're seeing are from 'sh'
but not from your node
19:38:24 <@tjfontaine> robertkowalski: does that make sense? iow change from spawn('sh'...
to spawn(process.execPath or execFile(process.execPath, and
you'll see the signal
```

After that commit every test for node 0.10 (0.8 still one missing) is running on travis, so we could start using travis for CI which could help us alot in daily work (e.g. pretesting PRs and giving automatic feedback, providing a single point of truth for tests). I tested it already with my github account, a run takes 7 minutes (including the old tests)