Rolf Lear

Let's consider a Java8-version of the build process where it would be nice to be able to do: ``` java SAXBuilder builder = new SAXBuilder(); Document doc = builder.build("path/to/data.xml"); doc.stream("/xpath/expression",...

@boneskull - I pulled your branch in to my local copy of mocha, I then npm link'd it in to my own project's npm repo, and ran the tests that...

@juergba - when the task completes: https://github.com/mochajs/mocha/blob/603da4464f34b58fb7bc96707680976b0f76cbe3/lib/runnable.js#L330

@boneskull - I ran in to the unit tests here hanging with --timeout 0 - as I mentioned in #3817. It may help you narrow down the issue... maybe. https://github.com/mochajs/mocha/blob/master/test/unit/mocha.spec.js#L281

@boneskull - re: > > I would prefer a root timer, similar to the one proposed by @rolfl. > > I'd have to see this working to be convinced it's...

@juergba - I should note that I can't remove the `--timeout 0` that WebStorm injects.... I'll initiate communication with them about it. Having said that, that would still just be...

@boneskull ... but why does setting --timeout 0 twice make it work again?

We have a bunch of tests that make http calls but the socket is unrefd in a low level library... these calls die. I cannot easily change this... and i...

@boneskull - I have played with the code a little to figure out what options are available. The underlying issue is that Mocha itself does not prevent exits when test...

@juergba - that's true, I could. On the other hand, I would have to add it to all files/tests because it is common when in the IDE doing TDD to...