Christopher Hiller

I note that `_enableTimeouts` is essentially a useless, internal flag that could be removed (across several different files) if we assume a `timeout` value of `0` is `false` and anything...

Unfortunately there's more to be done here. My guess is there's a problem with `--no-exit` / `--exit` behavior, as the builds seem to hang.

what I'm seeing is a hang in the `Runnable` unit tests around some edge-case stuff

alright, think I fixed that problem.

I'm going to sit on this until I get at least one review

> 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 the right choice. *UPDATE*: Let me...

> √ just kind of stops (9410ms) > √ just kind of stops (5798ms) >2 passing (15s) This is "slow" output. People using `--timeout 0` or `--timeout 99999999` don't usually...

> This way the --inspect-brk is consumed directly by node and is not piped through Mocha first. Therefore timeout=0 has to be set manually while debugging in order to avoid...

@rolfl I can't see what you did, but you can't just use `setTimeout` or `setInterval` without dereferencing it, e.g. `var setInterval = global.setInterval`, because Sinon (or Unexpected, or any other...

@juergba Would like to know if you are insistent on a "global" timer?