deasync causes premature termination of tests occasionally

[tolbertam]

Example

npm ERR! Windows_NT 6.3.9600
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "ci"
npm ERR! node v5.10.1
npm ERR! npm  v3.8.3
npm ERR! code ELIFECYCLE
npm ERR! cassandra-driver@3.0.2 ci: `mocha test/unit test/integration/short -R mocha-multi`
npm ERR! Exit status 3221225477
npm ERR! 
npm ERR! Failed at the cassandra-driver@3.0.2 ci script 'mocha test/unit test/integration/short -R mocha-multi'.
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 cassandra-driver package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     mocha test/unit test/integration/short -R mocha-multi
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs cassandra-driver
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls cassandra-driver
npm ERR! There is likely additional logging output above.

npm ERR! Please include the following file with any support request:

Possibly related to issue described in sass/node-sass#1283. We could consider following the same approaches, or perhaps consider removing the deasync dependency all together.

This reporter might be a better citizen if it didn't report tests individually anyways, so maybe we should use batches instead on some time interval (every 10 seconds or at some max size maybe?) in a separate timer anyways. The main thing will be to make sure any remaining tests are written before the reporter exits, which maybe challenging since mocha reporters are not callback driven. (similarly see #1)

[tolbertam]

Fixed in 0.2.1 by #8