Ok, now it's dying in provision.js

First run report (to save readers from having to wade through the travis logs):

• Node 4, Linux https://travis-ci.org/tessel/t2-cli/jobs/126171222
  • Pass
• Node 5, Linux https://travis-ci.org/tessel/t2-cli/jobs/126171223
  • Pass
• Node 4, OSX https://travis-ci.org/tessel/t2-cli/jobs/126171224
  • Stopped in provision.js
• Node 5, OSX https://travis-ci.org/tessel/t2-cli/jobs/126171225
  • Stopped in provision.js

Rerun report

• Node 4, Linux https://travis-ci.org/tessel/t2-cli/jobs/126171222
  • Pass
• Node 5, Linux https://travis-ci.org/tessel/t2-cli/jobs/126171223
  • Pass
• Node 4, OSX https://travis-ci.org/tessel/t2-cli/jobs/126171224
  • Stopped in provision.js
• Node 5, OSX https://travis-ci.org/tessel/t2-cli/jobs/126171225
  • Pass

Looks good - what instigated this PR?

My report about tests not completing on Node 5.x. Which @mattsoftware was running into on Slack. Seems there are a few issues open with tests just not completing all the way. Then when that happens Travis still reports it passed, because all the tests did pass, but not all were ran. Hopefully this can put a stop to all of that.

It was very good this was able to be reproduced locally, as it can be iterated on much faster than pushing and waiting for Travis.

It was very good this was able to be reproduced locally, as it can be iterated on much faster than pushing and waiting for Travis.

Sanity saver :)

My tests still seem to die even if I merge this patch into my repo. This time in/after controller.js

Same point if I run node v5.0.0 or v5.11.0

If you need me to provide any debugging etc let me know!

Whats your output if you run grunt -v?

This was only one part of a set of fixes...