tapjs
/
signal-exit
/
97
96%
|
Ran
|
Jobs
3
|
Files
2
|
Run time
39s
|
Badge
Embed ▾
README BADGES
|
push
travis-ci
isaacsDon't listen for SIGPIPE SIGPIPE normally doesn't cause node to exit [1]. However, by registering and unregistering a "SIGPIPE" event handler, the behavior changes and node starts exiting when receiving SIGPIPE signals. Because signal-exit listens for SIGPIPE, it causes programs to exit when receiving SIGPIPE, whereas normally node programs not using signal-exit should not exit when receiving SIGPIPE. This changes signal-exit to not listen for SIGPIPE and tests that a program using signal-exit will not exit due to SIGPIPE signals. The test uses an existing test fixture (test/fixtures/sigpipe.js) that was not previously being used. See also https://github.com/tapjs/signal-exit/issues/19. [1] https://github.com/nodejs/node/blame/44aba1ab1/doc/api/process.markdown#L243
81 of 84 relevant lines covered (96.43%)
580.55 hits per line
Jobs
| ID | Job ID | Ran | Files | Coverage | |
|---|---|---|---|---|---|
| 1 | 97.1 | 0 |
96.43 |
Travis Job 97.1 | |
| 2 | 97.2 | 0 |
96.43 |
Travis Job 97.2 | |
| 3 | 97.3 | 0 |
96.43 |
Travis Job 97.3 |
Source Files on build 97
Detailed source file information is not available for this build.