Skip to content

Instantly share code, notes, and snippets.

@JCBarry
Created November 29, 2011 21:53
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save JCBarry/1406726 to your computer and use it in GitHub Desktop.
Save JCBarry/1406726 to your computer and use it in GitHub Desktop.
ruby-1.9.2-p290:forever jbarry$ npm test
> forever@0.7.3 test /usr/local/lib/node_modules/forever
> vows --spec --isolate
♢ forever/spawn-options
When using forever an instance of forever.Monitor with valid options passing environment variables to env-vars.js
✓ should pass the environment variables to the child
When using forever an instance of forever.Monitor with valid options passing a custom cwd to custom-cwd.js
✓ should setup the child to run in the target directory
When using forever an instance of forever.Monitor with valid options setting hideEnv when spawning all-env-vars.js
✓ should hide the environment variables passed to the child
♢ forever
When using forever an instance of forever.Monitor with valid options
✓ should have correct properties set
When using forever attempting to start a script that doesn't exist
✓ should throw an error about the invalid file
When using forever checking if process exists if process process exists
✓ should return true
When using forever checking if process exists if process doesn't exist
✓ should return false
When using forever non-node usage with a perl one-liner
✓ should get back moo
When using forever an instance of forever.Monitor with valid options calling the restart() method in less than minUptime
✓ should restart the child process
When using forever running error-on-timer sample once
✓ should emit 'exit' when completed
When using forever running error-on-timer sample three times
✓ should emit 'exit' when completed
♢ forever/spin-restart
When using forever and spawning a script that spin restarts with a simple hook
✓ should raise the hook-exit event
♢ forever/multiple-processes
When using forever and spawning two processes using the same script
✓ should spawn both processes appropriately
♢ forever/service
When using forever the service module
✓ should have the correct exports
♢ forever/signal
When using forever and spawning a script that ignores signals SIGINT and SIGTERM with killTTL defined
✓ should forcibly kill the processes
♢ forever/spin-restart
When using forever and spawning a script that spin restarts with no spinSleepTime specified
✓ should spawn both processes appropriately
✓ should only run the bad process once
When using forever and spawning a script that spin restarts with a spinSleepTime specified
✓ should restart spinning processes
♢ forever/tail
node.js:134
throw e; // process.nextTick error, or 'error' event on first tick
^
SyntaxError: Unexpected end of input
at Object.parse (native)
at Socket.<anonymous> (/usr/local/lib/node_modules/forever/lib/forever.js:124:27)
at Socket.emit (events.js:64:17)
at Array.<anonymous> (net.js:831:12)
at EventEmitter._tickCallback (node.js:126:26)
♢ forever/watch
When using forever with watch enabled forever should
✓ have correct options set
When using forever with watch enabled forever should read .foreverignore file
✓ and store ignore patterns
When using forever with watch enabled forever should when file changes
✓ restart the script
When using forever with watch enabled forever should when file is added
✓ restart the script
When using forever with watch enabled forever should when file is removed
✓ restart the script
✗ Errored » 23 honored ∙ 1 errored (4.480s)
npm ERR! forever@0.7.3 test: `vows --spec --isolate`
npm ERR! `sh "-c" "vows --spec --isolate"` failed with 2
npm ERR!
npm ERR! Failed at the forever@0.7.3 test script.
npm ERR! This is most likely a problem with the forever package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! vows --spec --isolate
npm ERR! You can get their info via:
npm ERR! npm owner ls forever
npm ERR! There is likely additional logging output above.
npm ERR!
npm ERR! System Darwin 11.2.0
npm ERR! command "node" "/usr/local/bin/npm" "test"
npm ERR! cwd /usr/local/lib/node_modules/forever
npm ERR! node -v v0.4.12
npm ERR! npm -v 1.0.106
npm ERR! code ELIFECYCLE
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /usr/local/lib/node_modules/forever/npm-debug.log
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment