First revision.  Fails to reproduce error however.

So I thought this was a minimal representation of what we're doing, but
it fails to reproduce the issue.  I guess I'll have to hook in mocha and
see if that starts causing the issue.

Alternatively, it could be a ubuntu specific issue.  I first tested this
in my base OS instead of setting up a vagrant box.
Updated case to where the errant code is run by mocha + added vagrant

Since I wasn't reproducing the issue in my initial tests, I added mocha
into the mix.  That didn't reproduce the issue either.  However, adding
a ubuntu VM via vagrant to the case with mocha DID start reproducing the
issue.  The call to child_process.exec started creating 2 processes, the
first of which was a call to sh with the -c argument to execute the
actual command, presumably done this way so as to set the working
directory as specified in my code.

I'll strip out the working directory option to see if that makes the
issue go away.
Simplified case by removing working directory + renames for clarity

This still reproduces the issue on Ubuntu, even though I'm no longer
setting the working directory for the child process.  I also simplified
executing the test
Merge branch 'master' of https://github.com/thirdiron/repro_nodeJS_child_process_kill_bug

Not sure why this was a merge...

Conflicts:
	.gitignore
	app.js
	package.json