Christopher Hiller

@jorydotcom Thanks. Will do.

Consistency around the hook behavior is needed, but more importantly users just need to know what to expect. It doesn't work quite right atm, and there's an open discussion (though...

It's probably necessary, but I couldn't tell you why. Mocha does this in other places to compensate for the lack of tail call support in most JS runtimes & versions....

@overlookmotel I'm trying to get this fixed now.

cc @raymondfeng

I think my original comment was incorrect; it seems `setImmediate` *is* what we want to be doing. Either way, it needs to be consistent.

I've created #3631 which addresses the inconsistency, but it does not consume `process.nextTick()`; instead it uses `setImmediate()` in both cases. Please discuss further in that issue. cc @overlookmotel @meeber @raymondfeng

`--no-timeout` and `--timeout 0` are equivalent. Do your tests get ignored *outside* of webstorm when using `--inspect-brk`? cc @segrey

Ah, looks like you answered that.

The problem is with `unref()`. You said this doesn't happen in Mocha v5.x?